v0.1.5 — Thin Proxy Client

Non-breaking architecture change

@debridge-finance/debridge-mcp is no longer a standalone MCP server with local tool implementations. It is now a thin proxy client that connects to the hosted deBridge MCP endpoint at https://agents.debridge.com/mcp

All tools (get_instructions, search_tokens, get_supported_chains, create_tx, transaction_same_chain_swap), workflow skills, and resources are served by the hosted endpoint. The npm package simply bridges the gap for agent frameworks that cannot connect to a remote Streamable HTTP endpoint directly.

Recommended: if your agent supports Streamable HTTP, skip this package entirely and connect to the hosted endpoint https://agents.debridge.com/mcp

How the Proxy Works

• Stdio mode (default): Opens a long-lived MCP client connection to the upstream endpoint via StreamableHTTPClientTransport. Creates a local Server with StdioServerTransport that mirrors upstream capabilities and forwards tools/list, tools/call, resources/list, resources/read, and resources/templates/list requests.
• HTTP mode (MCP_TRANSPORT=http): Transparent HTTP reverse proxy via Express. Forwards raw JSON-RPC requests and SSE response streams, passing through Mcp-Session-Id headers for session continuity.

Tools and resources are dynamically discovered from the upstream at startup (stdio) or forwarded per-request (HTTP), so any updates to the hosted endpoint are reflected automatically without updating the package.

New environment Variable introduced: REMOTE_MCP_URL