Use Tavchain with AI

Connect your AI assistant to Tavchain Docs so it can search guides and read pages while you build. You do not need a wallet, API key or running node to access the public documentation.

Connect your assistant

Use the public documentation MCP endpoint:

https://docs.tavchain.safeney.com/mcp

Choose your client, or use Other clients for manual configuration in another compatible application or agent framework. Your client must support remote HTTP MCP servers.

Codex
Claude Code
Cursor
VS Code
Other clients

Add Tavchain Docs from your terminal:

codex mcp add tavchain-docs --url https://docs.tavchain.safeney.com/mcp

Run codex mcp list to check the configuration.

Run this command from your project directory:

claude mcp add --transport http tavchain-docs https://docs.tavchain.safeney.com/mcp

Open Claude Code and use /mcp to check the connection.

Add this entry to your project’s .cursor/mcp.json. If the file already contains other servers, keep those entries.

{
  "mcpServers": {
    "tavchain-docs": {
      "url": "https://docs.tavchain.safeney.com/mcp"
    }
  }
}

Enable the server in Cursor’s MCP settings.

With GitHub Copilot agent mode, add this entry to .vscode/mcp.json. Keep any existing servers.

{
  "servers": {
    "tavchain-docs": {
      "type": "http",
      "url": "https://docs.tavchain.safeney.com/mcp"
    }
  }
}

Start the server and enable its documentation tools in the agent’s tool picker.

In a client that supports remote MCP servers, enter:

Setting	Value
Name	`tavchain-docs`
Transport	Streamable HTTP (sometimes labelled HTTP)
Server URL	`https://docs.tavchain.safeney.com/mcp`
Authentication	None for public documentation

Save and enable the connection using your client’s instructions. Configuration-file keys differ between clients; keep existing server entries. Use the question below to check that the assistant can search the docs.

Try a question

Ask your assistant:

Use Tavchain Docs to find the current testnet chain ID and RPC URL.
Cite the network information page. Do not connect a wallet or send a transaction.

Check that the answer cites Network information and returns chain ID 771002 and RPC URL https://api.testnet.tavchain.safeney.com/. A configured server alone does not confirm that your assistant used it. You can also ask it to:

Find the Hardhat guide and explain how to compile and test a contract locally.
Read the installation choices and explain which package matches your operating system.
Explain how to check a transaction receipt using the JSON-RPC reference.

Use a page as context

Use Copy page beside a page title, or append .md to a documentation URL to read its Markdown version. The page menu also offers AI conversation and editor connection options. For assistants that fetch URLs, start with the documentation index. It lists pages so the assistant can retrieve the ones it needs. The full documentation text is available when you need broader context.

Documentation and blockchain access

The docs MCP searches published documentation. Its search and page-reading tools do not read live wallet balances, sign transactions or control your wallet. A separate feedback tool can submit documentation feedback when you request it. For live blocks, balances and receipts, connect the read-only blockchain MCP reader or use the Ethereum JSON-RPC API through an HTTP-capable tool or EVM library. Transaction signing requires a separate wallet or signer and your authorization. Keep private keys, seed phrases and passwords out of prompts and documentation feedback. Check cited pages and the selected network before following generated instructions.

Getting started

Smart contracts

Tools and resources

API reference

Help

Connect your assistant

Try a question

Use a page as context

Documentation and blockchain access