MCP Directory

How to add deBridge MCP to Cursor

Cross-chain and same-chain crypto swaps, fee estimation, and trade execution for AI agents via the deBridge protocol. Paste the config into ~/.cursor/mcp.json and restart Cursor.

Last updated June 14, 2026 · 31★ · stdio · no auth

Cursor config for deBridge MCP

npx -y @debridge-finance/debridge-mcp@latest
{
  "mcpServers": {
    "debridge-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@debridge-finance/debridge-mcp@latest"
      ]
    }
  }
}

Setup steps

  1. 1Open Cursor → Settings → MCP → Add new MCP server (or edit ~/.cursor/mcp.json directly).
  2. 2Paste the deBridge MCP config below into the "mcpServers" object.
  3. 3Fill in placeholder secrets, then save.
  4. 4Cursor reloads MCP servers automatically — check Settings → MCP for a green status dot.
  5. 5Ask Cursor to use one of deBridge MCP's tools to confirm it's connected.

Before you start

  • Node.js >= 18 (for the local npx/stdio proxy)
  • An MCP-compatible client (Claude Code, Claude Desktop/Web, Cursor, Windsurf, Cline, Continue, Zed, GitHub Copilot, etc.)
  • Docker (optional, only for running the HTTP proxy in a container)

What deBridge MCP can do in Cursor

get_instructions

Returns guidance/instructions for using the deBridge MCP and its workflows.

search_tokens

Searches for tokens available across supported chains.

get_supported_chains

Lists the blockchain networks supported by deBridge.

create_tx

Builds a cross-chain swap/transfer transaction via the deBridge protocol.

transaction_same_chain_swap

Builds a same-chain swap transaction.

Security

The npm package is a thin proxy client that forwards all requests to the hosted endpoint at https://agents.debridge.com/mcp (configurable via REMOTE_MCP_URL). Tools and resources are not implemented locally — they are discovered from the upstream endpoint. The server can build and execute cross-chain swaps and transfers, so review any transaction the agent constructs before signing or broadcasting it.

deBridge MCP + Cursor FAQ

Where is the Cursor config file?

Cursor reads MCP servers from ~/.cursor/mcp.json. Paste the deBridge MCP config there under the "mcpServers" key and restart the client.

Is deBridge MCP safe to use with Cursor?

The npm package is a thin proxy client that forwards all requests to the hosted endpoint at https://agents.debridge.com/mcp (configurable via REMOTE_MCP_URL). Tools and resources are not implemented locally — they are discovered from the upstream endpoint. The server can build and execute cross-chain swaps and transfers, so review any transaction the agent constructs before signing or broadcasting it.

Do I need to install anything to use deBridge MCP?

No. The recommended approach is to connect your agent directly to the hosted Streamable HTTP endpoint at https://agents.debridge.com/mcp. The npm package is only needed for agent frameworks that require a local stdio or HTTP process.

What does the npm package actually do?

It is a thin proxy client. In stdio mode (default) it opens a connection to the upstream hosted MCP server and forwards tools/list, tools/call, resources/list, resources/read, and resources/templates/list. In HTTP mode (MCP_TRANSPORT=http) it acts as a transparent reverse proxy. Tools and resources are not implemented locally.

Can I point the proxy at a different endpoint?

Yes. Set the REMOTE_MCP_URL environment variable (default https://agents.debridge.com/mcp). You can also set MCP_TRANSPORT (stdio or http), PORT, and HOST.

View repo Full deBridge MCP page