Azure + Amp: Complete MCP Integration
Azure is a MCP server that The Azure MCP Server gives MCP Clients access to key Azure services and tools like Azure Storage, Cosmos DB, the Azure CLI, and more..
When integrated with Amp, you can:
- Access Azure functionality through Amp
This guide provides step-by-step instructions to set up Azure in Amp, including configuration, examples, and troubleshooting.
What You'll Achieve
After completing this setup:
- Azure will be fully integrated and operational
- You can use Azure tools directly in Amp
- All Azure capabilities will be available for your workflows
Prerequisites
Before starting, ensure you have:
- Amp installed and configured
- Compatible operating system (macOS, Linux, Windows (WSL))
Installation
Step 1: Install Azure
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 Azure in Amp:
## Testing Your Setup
1. Launch Amp
2. Verify Azure is available in the tools list
3. Test basic Azure functionality
## Troubleshooting
### Common Issues
#### 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
#### Azure not appearing in Amp
**Symptoms:** Server not listed, Tools not available
**Cause:** Configuration or installation issue
**Solution:**
- Verify configuration syntax
- Check Azure installation
- Restart Amp
- Check logs for error messages
## Next Steps
Now that Azure is integrated with Amp:
- Explore all Azure capabilities through Amp
- Check out other MCP servers that work with Amp
- Join the MCP community for tips and support
- Consider contributing to Azure development
## Need Help?
- Search for [Azure documentation](https://www.mcpstack.org)
- Check the [Amp MCP guide](https://www.mcpstack.org/clients)
- Join the MCP community discussions