deBridge

What is deBridge?

deBridge is a Model Context Protocol (MCP) integration for AI agents that enables cross-chain and same-chain token swaps, fee estimation, and trade execution across major blockchain networks. It provides a hosted MCP endpoint at agents.debridge.com/mcp and an npm package acting as a thin proxy client for agent frameworks that require a local stdio or HTTP process.

How to use deBridge?

Connect your AI agent directly to the hosted Streamable HTTP endpoint at https://agents.debridge.com/mcp with no installation required. For agent frameworks that only support stdio transport, run the local proxy using npx -y @debridge-finance/debridge-mcp@latest or via Docker, then configure the agent with the appropriate transport mode.

Key features of deBridge

• Cross-chain and same-chain swap execution.
• Fee estimation before trade execution.
• Hosted MCP endpoint with Streamable HTTP transport.
• Local proxy for stdio-only agent frameworks.
• Tools: search_tokens, get_supported_chains, create_tx, and more.
• Workflow skills via MCP resources and llms.txt overview.

Use cases of deBridge

• AI agents performing cross-chain token swaps on major blockchains.
• Estimating swap fees and executing trades programmatically.
• Integrating with agent frameworks that only support stdio transport.
• Building autonomous trading or portfolio management agents.

FAQ from deBridge

What is the hosted MCP endpoint?

The hosted endpoint is https://agents.debridge.com/mcp, using Streamable HTTP transport. No installation is needed to connect directly.

How do I connect if my agent only supports stdio?

Use the npm package as a local proxy: run npx -y @debridge-finance/debridge-mcp@latest and configure your agent with stdio transport. The proxy forwards all requests to the hosted endpoint.

What tools are exposed by deBridge MCP?

The endpoint exposes tools: get_instructions, search_tokens, get_supported_chains, create_tx, and transaction_same_chain_swap.

What are the runtime requirements?

For direct HTTP connection, no local runtime is needed. For the local proxy, Node.js >=18 (or Docker) is required. The npm package runs on any system with Node.js.

How does the local proxy work?

The proxy runs a local MCP server that transparently forwards calls (tools/list, tools/call, resources/list, etc.) to the upstream hosted endpoint. It supports both stdio and HTTP transport modes, and any changes to the hosted endpoint are reflected automatically.