Rubic MCP Server gives Claude, Cursor, VS Code, and other MCP-compatible AI tools structured access
to cross-chain and on-chain token swaps — quote, simulate, build, sign, broadcast, and track transactions.
Rubic MCP Server gives Claude, Cursor, VS Code, and other MCP-compatible AI tools structured access
to cross-chain and on-chain token swaps — quote, simulate, build, sign, broadcast, and track transactions.
Non-custodial. Open-source.
* Chain count reflects supported routing paths. EVM chains support full execution, while non-EVM chains support quoting and browser fallback.
Add to Claude, Cursor, VS Code,
or any MCP client
Rubic’s MCP Server connects to popular MCP-compatible AI tools and developer environments, including Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Cline, Continue, and Zed.
Any MCP-compatible client that speaks stdio or streamable HTTP can connect.
Rubic MCP Server replaces browser actions with structured DeFi tools. Agents quote, simulate, build, and surface risks, while users approve and sign.
Typed inputs and outputs agents can reliably
plan against.
Semantic codes enable clean agent recovery
and decision branching.
Quote, build, sign, broadcast, and track as
separate tools for flexible agent control.
Discover routes, quotes, and calldata without
a private key.
Preview output, fees, and risk before
execution.
Keys stay local; non-EVM or manual flows fall
back to Rubic in-browser.
From config to broadcast in three predictable steps. The agent shows a preview before anything is signed.
Most DeFi MCP servers go straight from prompt to transaction.
Rubic’s MCP Server lets AI agents show their work first, with a preview before signing when the workflow requires it.
- Agent executes the swap immediately
- No fee breakdown before signing
- No risk assessment
- Generic error on failure
- “Agentic finance” marketing copy
- Agent simulates first, then shows a preview
- Total cost in USD: gas, protocol, and provider fees
- Risk level: low / medium / high
- Typed error codes for recovery
- Structured JSON data agents can verify
Real prompts, real flows. You describe the outcome, and the agent selects the tools.
Ask an AI agent to swap tokens between supported chains, compare routes, simulate the outcome, and proceed only after approval.
[rubic_simulate_swap]
Use Rubic’s MCP Server for same-chain token swaps where supported, with quoting, simulation, and transaction preparation via MCP tools.
[rubic_simulate_swap]
Compare swap routes by output, fees, providers, timing, and risk.
[rubic_get_routes]
Preview output, fees, gas, route details, and risk before signing.
[rubic_simulate_swap]
Rubic’s MCP Server supports cross-chain and on-chain swap workflows across a broad set of EVM and non-EVM ecosystems through Rubic’s routing infrastructure.
Why is Rubic MCP Server?
Which AI tools does it support?
Is it custodial?
How are private keys handled?
Which chains are supported?
Can AI agents execute swaps automatically?
How does swap simulation work?
Where can I get started?