> For the complete documentation index, see [llms.txt](https://docs-core.allbridge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-core.allbridge.io/ai/overview.md).

# Overview

### Allbridge MCP

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

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

### How they fit together

In a normal flow:

1. Ask Allbridge MCP to plan the transfer.
2. Review the route, fee, and next step.
3. Send the unsigned payload to Local Signer MCP if signing is needed.
4. Broadcast the signed payload and track the transfer.

### What this gives you

* Bridge planning can happen remotely.
* Private keys stay local.
* Docs lookup does not require wallet access.

### When to use which product

* 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

### Product links

* Allbridge MCP repository: [allbridge-io/allbridge-mcp](https://github.com/allbridge-io/allbridge-mcp)
* Allbridge MCP Docker image: [allbridge/io.allbridge.mcp](https://hub.docker.com/repository/docker/allbridge/io.allbridge.mcp/tags?name=latest)
* Local Signer repository: [allbridge-io/local-signer-mcp](https://github.com/allbridge-io/local-signer-mcp)
* Local Signer Docker image: [allbridge/local-signer-mcp](https://hub.docker.com/repository/docker/allbridge/local-signer-mcp/tags?name=latest)

### Product boundary

* **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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs-core.allbridge.io/ai/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.