> 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/allbridge-mcp/developer-assistant.md).

# Developer Assistant

Allbridge MCP includes a read-only developer assistant for integration work.

### What it helps with

Use it when you want to find the right source material for a question such as:

* how Allbridge Core works
* what a fee page explains
* how the SDK handles a Solana transfer
* how the REST API flow is structured
* which example matches a given client or chain

### What it does

The developer assistant narrows the search and points you at the right page, guide, or example.

It is useful when you want to move from a product question to the exact documentation that answers it.

### How it works

The normal flow is:

1. `search_allbridge_documentation`
2. `get_allbridge_product_summary`
3. `list_available_coding_resources`
4. `get_coding_resource_details`

### What it can search

The assistant covers these content scopes:

* `project-docs` for product pages, FAQs, audits, and ecosystem reports
* `sdk-integration` for SDK guides and SDK-facing examples
* `rest-api-integration` for REST API docs and implementation references
* `examples` for local usage examples and client configuration samples

### Related tool groups

* `bridge` for route planning, balance checks, execution jobs, and transfer tracking
* `dev` for read-only documentation and integration guidance
* `broadcast` for already signed transaction broadcast