Swap Stablecoins

Allbridge AI MCP

Two open-source MCP servers that let any agent
plan, sign, broadcast, and track a cross-chain
transfer — safely, with keys staying on the user's machine

Read the docs See quickstart GitHub

Cross-chain bridging,
built for AI agents.

Works with

Why Allbridge AI

An MCP surface that understands cross-chain

Every tool returns a structured envelope with typed errors and next-step hints, so an agent can drive a transfer end-to-end without guessing.

  • Plan any transfer

    Routes, quotes, messenger options, and a recommended path for 10+ chains — returned as structured JSON the agent can reason over.

  • Keys stay local

    Coordination is key-free by design. The local signer owns the wallets; nothing ever leaves the user's machine.

  • Explicit handoff

    Every execution step carries a handoff block telling the client exactly which server signs, which broadcasts, and which wallet to pick.

  • 7 chain families

    EVM, Solana, Tron, Algorand, Stacks, Soroban / Stellar, and Sui — one consistent interface across all of them.

  • Full lifecycle

    Preflight balances, submit approvals, bridge, handle Stellar trustlines or Algorand opt-ins, and poll status — all with one job.

  • Works everywhere

    stdio for Claude Desktop, Claude Code, Cursor, Windsurf, Cline, Continue, Zed, Goose. streamable-http + OAuth for hosted agents and remote connectors.

Developer support

Allbridge MCP helps developers ship integrations faster

It can guide client setup, review documentation and config examples, and inspect transfer history in Core Explorer by sender address, recipient address, transaction hash, or transfer ID.

Ship with fewer integration mistakes

Integration support

Use Allbridge MCP to validate the setup, check docs, and keep the integration path aligned with the published interface.

  • Integration help

    Helps wire clients, pick the right transport, and spot missing env vars or config mistakes before they reach production.

  • Docs review

    Checks documentation, examples, and setup notes so implementation matches the published interface instead of drifting.

  • Transfer lookup

    Searches Core Explorer by sender address, recipient address, transaction hash, or transfer ID to trace transfers quickly.

Find the transfer you need without guessing

Core Explorer

Use the question you actually have and let MCP narrow it down to the right transfer record.

  • Confirm a transfer
  • Trace by sender
  • Trace by recipient
  • Open from tx hash
User supportExplorer case
What happened to my transfer?
Start with a transaction hash or transfer ID and have MCP pull the full transfer story without searching chain by chain.
Sender traceExplorer case
Show transfers sent from this wallet
Use a sender address when the wallet owner needs a list of outgoing transfers, status, and the latest checkpoint.
Recipient traceExplorer case
Find all transfers received by this address
Use a recipient address when the receiving side is the only known detail and you need to reconstruct the route.
Tx lookupExplorer case
Which bridge action matches this hash?
Drop in the transaction hash to confirm whether it was a deposit, swap, or receive leg and where it finalized.
How to ask it
Ask for the sender, recipient, transaction hash, or transfer ID and let the agent resolve the trail from there.
Open Core Explorer
How it works

From user intent to confirmed transfer in five steps

The bridge flow is split deliberately: coordination stays key-free, signing stays local. An explicit handoff block on every step tells the client which server owns the next action.

  1. STEP01
    allbridge-mcp

    Plan

    Agent calls plan_bridge_transfer with source chain, destination chain, token, and amount. Gets normalized routes and a recommended option.

    plan_bridge_transfer
  2. STEP02
    allbridge-mcp

    Preflight

    check_bridge_balances verifies the sender can cover the amount and fees. If not, the agent asks for a top-up before going further.

    check_bridge_balances
  3. STEP03
    allbridge-mcp

    Build

    create_bridge_execution_job returns ordered, ready-to-sign steps plus a handoff block pointing at the signer and the wallet selector.

    create_bridge_execution_job
  4. STEP04
    local-signer-mcp

    Sign & broadcast

    Local Signer MCP signs each step with the configured wallet and submits it. The transaction hash comes back immediately.

    sign_and_broadcast_transaction
  5. STEP05
    allbridge-mcp

    Track

    get_transfer_status polls the Allbridge explorer until the receive side lands. The agent streams the state back to the user.

    get_transfer_status
Quickstart

Two servers. One client config.

Allbridge MCP runs hosted at mcp.allbridge.io. The signer runs on your machine as a Docker container, so private keys never leave it. Wire both into any MCP-capable client in three steps.

  1. 01 Pull the signer image

    The signer runs on your machine so private keys never leave it. Pull the latest image from Docker Hub.

    bash
    docker pull allbridge/local-signer-mcp:latest

  2. 02 Create a wallet env file

    Save your keys and RPC URLs at ~/.allbridge/signer.env. One line per chain family — include only the ones you need.

    dotenv
    # ~/.allbridge/signer.env

# EVM (Ethereum, BSC, Polygon, Arbitrum, Optimism, Base …)
LOCAL_SIGNER_EVM_PRIVATE_KEY=0x...
LOCAL_SIGNER_EVM_RPC_URL=https://rpc.example.org

# Solana
LOCAL_SIGNER_SOLANA_PRIVATE_KEY=...base58...
LOCAL_SIGNER_SOLANA_RPC_URL=https://api.mainnet-beta.solana.com

# Tron / Algorand / Stacks / Soroban / Sui — same pattern.
# Full reference: docs-core.allbridge.io/ai/local-signer-mcp

03 Register both servers in your client

Same two servers, native config for the client you use.

Claude Code

Register both servers in a couple of CLI lines. Restart Claude Code when done.

# Hosted Allbridge MCP — coordination
claude mcp add --transport http allbridge https://mcp.allbridge.io/

# Local signer — Docker image, keys stay on your machine
claude mcp add local-signer -- \
  docker run --rm -i \
    --env-file "$HOME/.allbridge/signer.env" \
    allbridge/local-signer-mcp:latest

Full environment reference, hosted deployment notes, and self-host instructions live in the documentation.

Open source.
Ready today.

Two repos, one mission: hosted coordination you don't have to run, and a local signer that keeps keys on your machine. Fork either, audit either, deploy either.

  • MITLicense
  • 7Chain families
  • 10+MCP clients
  • 0Keys uploaded
Read the docs
Coordinationallbridge-io / allbridge-mcpHosted at mcp.allbridge.io
Signingallbridge-io / local-signer-mcpRuns locally — keys never leave
docker pull local-signer-mcp Try in Claude (plan only — signing needs local-signer)

Our socials

Need assistance?

Copyright © 2026 All rights reserved. Allbridge