> For the complete documentation index, see [llms.txt](https://developer.trustwallet.com/developer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.trustwallet.com/developer/mcp.md).

# MCP Servers

Trust Wallet publishes two [Model Context Protocol (MCP)](https://modelcontextprotocol.io) servers for AI coding assistants:

* [**Docs MCP**](/developer/mcp/docs-mcp.md) — search and retrieve content from the full Trust Wallet developer documentation. Powered by GitBook; no API key required.
* [**API Gateway MCP**](/developer/mcp/api-gateway.md) — query live blockchain data: token prices, swap quotes, trending tokens, address security checks, and more. Requires API credentials from [portal.trustwallet.com](https://portal.trustwallet.com).

## Which one should I use?

Use the **Docs MCP** when you want your AI assistant to answer questions about Trust Wallet's developer documentation — integration guides, Wallet Core, asset listing, and so on.

Use the **API Gateway MCP** when you want your AI agent to interact with live blockchain data and crypto services programmatically.

Both servers can be active at the same time.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.trustwallet.com/developer/mcp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.