debridge-finance/debridge-mcp

deBridge MCP integration for AI agents — cross-chain and same-chain swaps, fee estimation, and trade execution across major blockchain networks.
The hosted MCP endpoint is available at agents.debridge.com. This npm package is a thin proxy client for agents that require a local stdio or HTTP process.
https://github.com/user-attachments/assets/8ebe88ff-db3c-455e-9efb-50389e4bf5bd
Connecting to deBridge MCP
Recommended: Direct connection (Streamable HTTP)
Connect your agent directly to the hosted endpoint — no installation, no local process:
This is a Streamable HTTP MCP endpoint. It exposes tools (get_instructions, search_tokens, get_supported_chains, create_tx, transaction_same_chain_swap), workflow skills via MCP resources, and an llms.txt overview. Tools and skills are maintained in the debridge-finance/debridge-skills repository.
**Generic Streamable HTTP configuration:**
Claude Code (CLI & IDE plugins)
Verify:
Claude Web & Desktop Apps
Add as a remote MCP server with the URL https://agents.debridge.com/mcp.
Cursor
Add to .cursor/mcp.json in your project or ~/.cursor/mcp.json globally:
GitHub Copilot (VS Code Chat)
Add to .vscode/mcp.json in your workspace:
Windsurf
Add to ~/.codeium/windsurf/mcp_config.json:
Cline
Open Cline settings in VS Code, go to MCP Servers, click "Edit MCP Settings" and add:
Continue
Add to ~/.continue/config.json:
Zed
Add to your Zed settings (~/.config/zed/settings.json):
OpenClaw (via mcp-adapter plugin)
Install the mcp-adapter plugin:
Add to ~/.openclaw/openclaw.json:
---
Alternative: Run a local proxy
Some agent frameworks only support stdio transport and cannot connect to a remote HTTP endpoint directly. This npm package bridges that gap — it runs a local MCP process that transparently proxies all requests to https://agents.debridge.com/mcp.
Tools and resources are not implemented locally. They are dynamically discovered from the upstream endpoint at startup (stdio) or forwarded per-request (HTTP), so any changes to the hosted MCPd are reflected automatically without updating the package.
How the proxy works
- **Stdio mode** (default): Opens a long-lived MCP client connection to the upstream MCPd via StreamableHTTPClientTransport. Creates a local Server with StdioServerTransport that mirrors the upstream capabilities and forwards tools/list, tools/call, resources/list, resources/read, and resources/templates/list to the upstream.
- **HTTP mode** (MCP_TRANSPORT=http): Transparent HTTP reverse proxy via Express. Forwards raw JSON-RPC requests and SSE response streams to the upstream MCPd, passing through Mcp-Session-Id headers for session continuity.