> ## Documentation Index
> Fetch the complete documentation index at: https://sdk.docs.xano.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Docs for agents

> Give a coding agent these docs as llms.txt, llms-full.txt, a Markdown copy of any page, or the site's hosted MCP server, and know when to use the SDK's own in-package docs instead.

This site serves every page in forms an agent can read directly. Use them for the journeys:
setting up a project, running it on the Xano Engine, shipping a release. For the exact API of the
SDK version a project has installed, the agent should read the docs inside the package (see
[below](#in-package-docs-come-first-for-the-api)).

## What the site serves

| URL | What it holds |
| - | - |
| `https://sdk.docs.xano.com/llms.txt` | An index of every page in navigation order, each with its title, link and one-sentence description. |
| `https://sdk.docs.xano.com/llms-full.txt` | Every page's full content in one file. |
| Any page URL plus `.md` | That page as Markdown, for example `https://sdk.docs.xano.com/ship/releases.md`. |
| `https://sdk.docs.xano.com/mcp` | A hosted MCP server that searches and reads these docs. |

The `llms.txt` links already point at the `.md` copies, so an agent that starts there can fetch
any page without parsing HTML. Both files are generated from the published site and stay current
with it.

## Connect the docs MCP server

The server lets an agent search these docs and read a page while it works, instead of you pasting
pages into the chat. It is a remote HTTP server; no install and no sign-in.

<Tabs>
  <Tab title="Claude Code">
    ```bash theme={null}
    claude mcp add --transport http xano-sdk-docs https://sdk.docs.xano.com/mcp
    claude mcp list
    ```
  </Tab>

  <Tab title="Cursor">
    Open the command palette, run **Open MCP settings**, choose **Add custom MCP**, and add the
    server to `mcp.json`:

    ```json theme={null}
    {
      "mcpServers": {
        "xano-sdk-docs": {
          "url": "https://sdk.docs.xano.com/mcp"
        }
      }
    }
    ```
  </Tab>

  <Tab title="VS Code">
    Add the server to `.vscode/mcp.json`:

    ```json theme={null}
    {
      "servers": {
        "xano-sdk-docs": {
          "type": "http",
          "url": "https://sdk.docs.xano.com/mcp"
        }
      }
    }
    ```
  </Tab>

  <Tab title="Claude">
    In Claude's settings, open **Connectors**, choose **Add custom connector**, name it
    `xano-sdk-docs`, and enter `https://sdk.docs.xano.com/mcp` as the URL.
  </Tab>
</Tabs>

Other agents take the same URL as a remote (HTTP) MCP server. The page menu described below can
also copy the URL or connect Cursor for you.

This server is not the Xano Engine's MCP server: that one runs on your machine and works on your
backend. See [Engine MCP server](/run/engine-mcp), and the note on
[Coding agents](/ai/coding-agents#let-the-agent-run-the-backend) for all three servers you may
meet.

## The page menu

The menu at the top of each page hands the page to an AI tool:

| Option | What it does |
| - | - |
| **Copy page** | Copies the page as Markdown. |
| **View as Markdown** | Opens the `.md` copy of the page. |
| **Open in Claude** | Starts a Claude conversation with the page as context. |
| **Open in ChatGPT** | Starts a ChatGPT conversation with the page as context. |
| **Connect to Cursor** | Installs this site's MCP server in Cursor. |
| **Copy MCP server URL** | Copies `https://sdk.docs.xano.com/mcp`. |

## In-package docs come first for the API

`@xano/sdk` ships its own agent docs, written for the exact version installed:

| File | Use it for |
| - | - |
| `node_modules/@xano/sdk/llms.txt` | The mental model, the deploy contract and the gotchas, plus a list of topic files and when to open each. |
| `node_modules/@xano/sdk/llms/*.md` | One surface in depth: statements, fields, filters, tests, triggers, errors. |
| `node_modules/@xano/sdk/llms-full.txt` | All of the above in one file. |
| `node_modules/@xano/sdk/manifest.json` | One entry's full detail, looked up with `jq`: a statement's fields, a filter's arguments, a CLI command's flags. |

Prefer these whenever the question is "what is the exact builder, option or flag". They cannot
disagree with the code the agent is compiling against, while this site documents one SDK version
at a time. Use this site for the "how do I" questions: the order of steps, which command to run
for which target, and what to do when something fails.

A project made with `init` already tells its agent to read the in-package files, in its managed
`AGENTS.md`. See [Coding agents](/ai/coding-agents#what-the-agent-reads).

## Next

* Set up your coding agent with the agent skill and `AGENTS.md`: [Coding agents](/ai/coding-agents).
* Look up a command or flag: [CLI reference](/reference/cli/index).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.