Usage

Local Signer MCP is used after another system has prepared an unsigned payload.

Common flow

1. An orchestration layer creates an unsigned transaction or bridge step.

2. Local Signer MCP signs the payload locally.

3. The signed payload is broadcast by the appropriate system or client.

Supported execution patterns

• sign only

• sign and broadcast

• broadcast an already signed transaction

Tools

• get_wallet_capabilities shows which wallet families and accounts are configured.

• get_accounts returns configured local account addresses.

• sign_transaction signs an unsigned transaction and returns the signed payload.

• broadcast_transaction submits an already signed payload.

• sign_and_broadcast_transaction signs locally and submits in one step.

Operational rule

Do not move signing logic into the orchestration layer.

Keep bridge planning in Allbridge MCP and local execution in Local Signer MCP.