Overview
Allbridge uses two MCP products for AI-assisted bridge flows.
Last updated
Allbridge uses two MCP products for AI-assisted bridge flows.
Allbridge MCP is the coordination layer.
It helps you:
plan the route
check balances
build the execution step
find the right docs or example
broadcast a payload that is already signed
track the transfer after submission
Local Signer MCP is the local signing layer.
It helps you:
sign the payload on the user's machine
keep private keys out of the network path
finish a flow that another system already prepared
In a normal flow:
Ask Allbridge MCP to plan the transfer.
Review the route, fee, and next step.
Send the unsigned payload to Local Signer MCP if signing is needed.
Broadcast the signed payload and track the transfer.
Bridge planning can happen remotely.
Private keys stay local.
Docs lookup does not require wallet access.
Use Allbridge MCP when you need to:
discover supported chains and tokens
plan a bridge route
check balances before execution
build the next execution step
look up docs, examples, and integration references
broadcast a payload that is already signed
Use Local Signer MCP when you need to:
sign a transaction locally
keep private keys off the network
connect a desktop MCP client to a local wallet
finish a flow prepared by another system
Allbridge MCP repository: allbridge-io/allbridge-mcp
Allbridge MCP Docker image: allbridge/io.allbridge.mcp
Local Signer repository: allbridge-io/local-signer-mcp
Local Signer Docker image: allbridge/local-signer-mcp
Allbridge MCP handles route planning, documentation, and bridge coordination.
Local Signer MCP handles local signing and local wallet execution.
Private keys stay with Local Signer MCP.
Orchestration and docs stay with Allbridge MCP.
Start with the product page that matches the task you want to solve.
Last updated