
Wormhole Mcp
Give your agent Wormhole bridge and cross-chain transfer context while building multi-chain apps or bridge monitors.
Overview
Wormhole MCP is a MCP server for the Build phase that offers 69 tools for cross-chain transfers and Wormhole bridge data.
What is this MCP server?
- 69 MCP tools for cross-chain transfers and Wormhole bridge data
- Hosted streamable-http at wormhole.mcp.junct.dev
- Version 1.1.0 with repository junct-bot/wormhole-mcp
- Broadest tool surface in this junct-bot DeFi MCP set for bridge operations research
- Bridge and transfer data via MCP—not a substitute for audited bridge transaction signing
- 69 MCP tools for cross-chain transfers and bridge data
- Server version 1.1.0
- Remote URL https://wormhole.mcp.junct.dev/mcp
Community signal: 1 GitHub stars.
What problem does it solve?
Multi-chain features break when agents lack structured Wormhole bridge and transfer data and instead improvise risky cross-chain guidance.
Who is it for?
Solo builders integrating Wormhole, debugging bridge flows, or prototyping cross-chain agents with a large typed tool surface.
Skip if: Beginners seeking a single-click bridge app or teams that need guaranteed finality without custom ops and key management.
What do I get? / Deliverables
You register the Wormhole remote and unlock sixty-nine MCP tools for cross-chain and bridge queries inside your agent workflow.
- Wormhole MCP remote registered in the agent
- Access to 69 bridge and transfer-oriented tools
- Agent-grounded cross-chain integration research
Recommended MCP Servers
Journey fit
Wormhole MCP is shelved under Build because cross-chain tooling is adopted when implementing bridges or multi-chain flows, not during casual ideation. Integrations is the right subphase for large protocol MCP surfaces (69 tools) wired into agent-driven development.
How it compares
Cross-chain bridge data MCP with 69 tools, not a wallet skill or generic L1 RPC wrapper.
Common Questions / FAQ
Who is Wormhole MCP for?
It is for developers building multi-chain products who want Wormhole transfer and bridge data callable from Claude Code, Cursor, or similar MCP clients.
When should I use Wormhole MCP?
Use it during Build integrations when designing, testing, or documenting Wormhole cross-chain paths and bridge-related behavior.
How do I add Wormhole MCP to my agent?
Add https://wormhole.mcp.junct.dev/mcp as a streamable-http MCP server in your agent configuration.