Skip to main content

​
Other

Any MCP-compatible client can connect to Danube using these settings:
SettingValue
URLhttps://danube.fastmcp.app/mcp
TransportHTTP with SSE
Auth Headerdanube-api-key

​
Amazon Q IDE

Amazon Q Developer supports MCP for enhanced AI assistance. 
{
  "mcpServers": {
    "danube": {
      "url": "https://danube.fastmcp.app/mcp",
      "headers": {
        "danube-api-key": "YOUR_API_KEY"
      }
    }
  }
}

​
Amp (Sourcegraph)

Amp is Sourcegraph’s AI coding assistant with MCP support. 
{
  "mcpServers": {
    "danube": {
      "url": "https://danube.fastmcp.app/mcp",
      "headers": {
        "danube-api-key": "YOUR_API_KEY"
      }
    }
  }
}

​
Generic Configuration

For any other MCP client, use this standard configuration format: 
{
  "mcpServers": {
    "danube": {
      "url": "https://danube.fastmcp.app/mcp",
      "headers": {
        "danube-api-key": "YOUR_API_KEY"
      }
    }
  }
}

​
Stdio-Only Clients

If your MCP client only supports stdio transport (local servers), use the mcp-remote npm package to bridge to Danube’s remote server.
This requires Node.js 18+ installed on your system.
{
  "mcpServers": {
    "danube": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://danube.fastmcp.app/mcp",
        "--header",
        "danube-api-key:YOUR_API_KEY"
      ]
    }
  }
}
The mcp-remote package:
  • Runs as a local stdio process
  • Proxies requests to Danube’s remote HTTP/SSE server
  • Handles authentication via the --header flag

​
Troubleshooting

  • Test: curl https://danube.fastmcp.app/health
  • Check firewall/VPN settings
  • Ensure HTTPS port 443 is allowed
  • Verify your API key is correct
  • Ensure the header name is exactly danube-api-key (lowercase)
  • Try generating a new API key
Use the mcp-remote wrapper as shown in the “Stdio-Only Clients” section above. This bridges stdio-based clients to Danube’s HTTP/SSE server.
  • Ensure Node.js 18+ is installed: node --version
  • Clear the mcp-remote cache: rm -rf ~/.mcp-auth
  • Try adding -y flag to auto-accept npx installation