> For the complete documentation index, see [llms.txt](https://docs-v4.nftx.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-v4.nftx.io/agentic-development/mcp-server.md).

# Connect via MCP

GitBook publishes these docs with a hosted **Model Context Protocol (MCP)** server — a standard interface that lets an AI client search and read the documentation directly, in real time. Point your agent at it and questions about NFTX get answered from *this* site, not from a stale training snapshot.

## The endpoint

```
https://gitbook.flaunch.gg/nftx/~gitbook/mcp
```

It's **read-only**: a connected client can search the docs, retrieve specific pages, and answer questions from the published content. Nothing it does can change the docs or touch the chain.

{% hint style="info" %}
This is the endpoint for public content. GitBook also exposes `…/~gitbook/mcp/auth` for sites that gate part of their content behind authentication — you won't need it for these public docs.
{% endhint %}

## Add it to your client

Every AI tool configures MCP servers a little differently, but it comes down to handing it the URL above. A few common ones:

{% tabs %}
{% tab title="Claude Code" %}

```bash
claude mcp add --transport http nftx-docs https://gitbook.flaunch.gg/nftx/~gitbook/mcp
```

Then start a session and ask about NFTX — the agent calls the docs server whenever it needs an answer.
{% endtab %}

{% tab title="Cursor / VS Code" %}
Add the server to your MCP config (for example `.cursor/mcp.json` or `.vscode/mcp.json`):

```json
{
  "mcpServers": {
    "nftx-docs": {
      "url": "https://gitbook.flaunch.gg/nftx/~gitbook/mcp"
    }
  }
}
```

{% endtab %}

{% tab title="Claude Desktop" %}
Claude Desktop reaches remote servers through the `mcp-remote` bridge. In `claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "nftx-docs": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://gitbook.flaunch.gg/nftx/~gitbook/mcp"]
    }
  }
}
```

{% endtab %}
{% endtabs %}

For anything else, check your tool's own MCP setup guide and use the endpoint above.

## What to do with it

Once connected, ask the way you'd ask a teammate who has read all the docs:

* "How does the NFTX listing tax scale with the floor multiple?"
* "What's the Locker's `redeem` signature, and which contract holds it?"
* "Which endpoint returns a swap quote and calldata?"

The agent searches the docs, pulls the relevant pages, and answers from them. For the underlying files those answers are built from, see [LLM-Ready Docs](/agentic-development/llm-ready-docs.md).