Local Signing

Allbridge MCP does not sign transactions.

When bridge execution produces an unsigned payload, hand it off to Local Signer MCP on the user's machine.

The handoff

The normal flow is simple:

• Allbridge MCP plans the route and returns the job

• the job includes an unsigned step and wallet hints

• Local Signer MCP signs that step locally

• the signed result is then broadcast

What to look for in the job

The execution job usually includes:

• walletSelector hints

• walletId when one wallet should be pinned

• the chain family of the source step

• the transaction shape for the next step

What this page does not cover

• private key material

• wallet signing logic

• local account storage

Keep signing in the separate signer project. Keep orchestration and route planning in Allbridge MCP.