> For the complete documentation index, see [llms.txt](https://docs.zetrix.com/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zetrix.com/en/developer-resources/zetrix-mcp-server.md). # Zetrix MCP Server The **Zetrix MCP Server** enables developers to build, test, and interact with blockchain applications using natural language conversations with AI assistants such as Claude. Instead of manually navigating RPC endpoints, writing boilerplate scripts, or switching tools, developers can simply *ask* the AI to perform actions such as querying account balances, generating smart contracts, monitoring blockchain activity, or signing transactions. This is made possible through the **Model Context Protocol (MCP)**, which acts as a bridge between AI tools and the Zetrix blockchain. With the Zetrix MCP Server, every aspect of Zetrix development becomes conversational, automated, and accessible. This creates an **AI-assisted blockchain development environment**, enabling natural-language-driven workflows without manually referencing RPC documentation or switching between tools. --- # 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, and the optional `goal` query parameter: ``` GET https://docs.zetrix.com/en/developer-resources/zetrix-mcp-server.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.