Skip to main content
Any MCP-compatible client can connect to Danube using these settings:

​
VS Code

VS Code’s built-in MCP support (Copilot agent mode) reads servers from .vscode/mcp.json in your workspace, or from your user settings via MCP: Add Server.
Run MCP: List Servers from the command palette to confirm Danube is connected, then ask Copilot to search for a tool.

​
Amazon Q IDE

Amazon Q Developer supports MCP for enhanced AI assistance.

​
Amp (Sourcegraph)

Amp is Sourcegraph’s AI coding assistant with MCP support.

​
Fewer tools per session

Danube exposes 33 tools. Every one of them is described to your model at the start of a session, which costs context. If a client only needs discovery and execution, ask for the core group on the connection URL:
Groups: core (the 11 discovery, execution and context tools: get_context, search_tools, list_services, get_service_tools, describe_tool, execute_tool, batch_execute_tools, fetch_result, store_credential, report_tool, set_parameter_defaults), skills (5), workflows (6), wallet (6), feedback (4), context (1: update_context, which writes your personal context). Combine them with commas (?tools=core,workflows). core is always included, and leaving the parameter off keeps the full list.

​
Generic Configuration

For any other MCP client, use this standard configuration format:

​
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.
The mcp-remote package:
  • Runs as a local stdio process
  • Proxies requests to Danube’s remote streamable HTTP server
  • Handles authentication via the --header flag

​
Troubleshooting

  • Test: curl https://mcp.danubeai.com/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 streamable HTTP 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