APIWeaver + Amp: Complete MCP Integration
APIWeaver is a MCP server that An MCP server that dynamically creates MCP servers from web API configurations. This allows you to easily integrate any REST API, GraphQL endpoint, or web service into an MCP-compatible tool that can be used by AI assistants like Claude..
When integrated with Amp, you can:
- Register and configure APIs at runtime without server restart
- Support for REST APIs, GraphQL endpoints, and web services
- Multiple authentication methods for different API requirements
This guide provides step-by-step instructions to set up APIWeaver in Amp, including configuration, examples, and troubleshooting.
What You'll Achieve
After completing this setup:
- APIWeaver will be fully integrated and operational
- You can use APIWeaver tools directly in Amp
- All APIWeaver capabilities will be available for your workflows
- Access to 6 different tools
Prerequisites
Before starting, ensure you have:
- Amp installed and configured
- Compatible operating system (macOS, Linux, Windows (WSL))
Installation
Step 1: Install APIWeaver
Configuration
Step 2: Configure Amp
-
Locate your configuration file:
-
Add server configuration:
Configure MCP servers in VS Code/Cursor settings.json:
```json
{
"amp.mcpServers": {
"playwright": {
"command": "npx",
"args": ["-y", "@playwright/mcp@latest", "--headless", "--isolated"]
},
"semgrep": {
"url": "https://mcp.semgrep.ai/mcp"
},
"sourcegraph": {
"url": "${SRC_ENDPOINT}/.api/mcp/v1",
"headers": {
"Authorization": "token ${SRC_ACCESS_TOKEN}"
}
},
"linear": {
"command": "npx",
"args": ["mcp-remote", "https://mcp.linear.app/sse"]
}
}
}
Or add servers via CLI:
# Add HTTP-based server
amp mcp add sourcegraph --header "Authorization=token your-token" https://sourcegraph.example.com/.api/mcp/v1
# Add SSE-based server
amp mcp add linear https://mcp.linear.app/sse
# OAuth login for authenticated servers
amp mcp oauth login my-server \
--server-url https://example.com/.api/mcp/v1 \
--client-id your-client-id \
--client-secret your-client-secret \
--scopes "openid,profile,email"
3. **Restart Amp**
Completely quit and restart Amp to load the new configuration.
## Examples
Once configured, you can use APIWeaver in Amp:
### Register REST API with Authentication
Add a REST API with Bearer token authentication
**Ask Amp:** "Register the JSONPlaceholder API (https://jsonplaceholder.typicode.com) with GET and POST methods"
**Expected Result:** API registered successfully with auto-generated tools for posts, users, and comments endpoints
### GraphQL Endpoint Integration
Connect to a GraphQL API for data querying
**Ask Amp:** "Register the GitHub GraphQL API with authentication and create tools for repository queries"
**Expected Result:** GraphQL endpoint configured with query tools for repositories, issues, and user data
### API Testing and Validation
Test API connectivity before integration
**Ask Amp:** "Test connection to the Stripe API with my API key before registering it"
**Expected Result:** Connection test successful with API schema validation and endpoint verification
### Multi-API Workflow
Integrate multiple APIs for complex workflows
**Ask Amp:** "Register both Twitter API and SendGrid API to create a workflow for social media monitoring and email alerts"
**Expected Result:** Both APIs registered with tools for tweet monitoring, email sending, and automated workflow execution
## Testing Your Setup
1. Launch Amp
2. Verify APIWeaver is available in the tools list
3. Test basic APIWeaver functionality
## Troubleshooting
### Common Issues
#### API Registration Failed
**Symptoms:** Registration errors, Invalid API configuration, Connection timeouts
**Cause:** Incorrect API URL, authentication issues, or network problems
**Solution:**
- Verify API endpoint URL is accessible
- Check authentication credentials are valid
- Test API manually with curl or Postman first
- Ensure network connectivity and firewall settings
#### Authentication Not Working
**Symptoms:** 401 Unauthorized, 403 Forbidden, Auth token invalid
**Cause:** Incorrect authentication method or invalid credentials
**Solution:**
- Verify authentication method matches API requirements
- Check API key/token is not expired
- Confirm header format and parameter names
- Test authentication with API documentation examples
#### Transport Mode Not Connecting
**Symptoms:** Connection refused, Transport errors, Client not recognizing server
**Cause:** Incorrect transport configuration or port conflicts
**Solution:**
- Use streamable-http for modern clients
- Check port is not in use: netstat -an | grep :8000
- Verify host/port settings match client configuration
- Try different transport modes (stdio/http/sse)
#### Python Dependencies Missing
**Symptoms:** Import errors, Module not found, Package installation failures
**Cause:** Missing Python packages or virtual environment issues
**Solution:**
- Install requirements: pip install -r requirements.txt
- Create virtual environment: python -m venv apiweaver-env
- Activate environment before installation
- Upgrade pip: python -m pip install --upgrade pip
#### API Schema Generation Failed
**Symptoms:** Tool generation errors, Schema parsing failures, Endpoint mapping issues
**Cause:** Unsupported API format or incomplete API documentation
**Solution:**
- Provide OpenAPI/Swagger specification if available
- Start with simple GET endpoints first
- Manually configure complex APIs step by step
- Check API documentation for required parameters
#### MCP Server Not Connecting
**Symptoms:** Server not appearing in tools, Connection timeout, Authentication errors
**Cause:** Invalid configuration, missing credentials, or network issues
**Solution:**
- Verify server URL and command are correct
- Check environment variables are set properly
- For OAuth servers, run amp mcp oauth login
- Review amp logs for error messages
#### Tool Execution Fails
**Symptoms:** MCP tools available but not working, Error messages during execution
**Cause:** Server dependencies missing or permission issues
**Solution:**
- Verify required environment variables are configured
- Check amp.permissions settings for tool restrictions
- Test MCP server independently
- Review server-specific documentation
#### Permission Denied
**Symptoms:** Tool blocked by permission system, Ask prompts for every action
**Cause:** Permission rules restricting MCP tool usage
**Solution:**
- Review amp.permissions in settings.json
- Add allow rules for trusted MCP servers
- Use amp permissions edit to modify rules
#### APIWeaver not appearing in Amp
**Symptoms:** Server not listed, Tools not available
**Cause:** Configuration or installation issue
**Solution:**
- Verify configuration syntax
- Check APIWeaver installation
- Restart Amp
- Check logs for error messages
## Next Steps
Now that APIWeaver is integrated with Amp:
- Explore all APIWeaver capabilities through Amp
- Check out other MCP servers that work with Amp
- Join the MCP community for tips and support
- Consider contributing to APIWeaver development
## Need Help?
- Search for [APIWeaver documentation](https://www.mcpstack.org)
- Check the [Amp MCP guide](https://www.mcpstack.org/clients)
- Join the MCP community discussions