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

# Use these docs with your AI agent

> How MCP Manager publishes its documentation for AI agents — a hosted docs MCP server, an agent skill (skill.md), llms.txt, and per-page Markdown — so your developers' coding agents can self-serve accurate, always-current answers about the platform, and how to register the docs MCP server behind your own MCP Manager gateway to govern that access.

Most documentation is written for people. **MCP Manager**'s documentation is also built to be read by **AI agents** — every page is published in machine-readable form and as a live MCP server, so the coding agents your developers already use can answer questions like *"does MCP Manager offer PII redaction?"* or *"how do I set up SCIM provisioning?"* straight from the current docs.

## What MCP Manager publishes for AI

| Surface                | Where                                        | What it is for                                                                         |
| ---------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------- |
| **Docs MCP server**    | `https://docs.mcpmanager.ai/mcp`             | A remote MCP endpoint your agent queries to search and read the live docs in context.  |
| **Agent skill**        | `https://docs.mcpmanager.ai/skill.md`        | An operating manual that teaches an agent how to drive MCP Manager correctly.          |
| **`llms.txt`**         | `https://docs.mcpmanager.ai/llms.txt`        | A structured index of every page, so an agent can discover what exists.                |
| **`llms-full.txt`**    | `https://docs.mcpmanager.ai/llms-full.txt`   | The entire documentation corpus in one file, for bulk ingestion.                       |
| **Per-page Markdown**  | append `.md` to any page URL                 | The raw Markdown of a single page — for example `/features/gateway-rules/overview.md`. |
| **Discovery document** | `https://docs.mcpmanager.ai/.well-known/mcp` | Lets agents locate the MCP server automatically, with no manual configuration.         |

The two surfaces that matter most are the **docs MCP server** — so an agent can read the docs live — and the **agent skill** — so an agent knows how to act on them. Both are covered below. The property they all share is that they are **regenerated on every publish**, so an agent reading them always sees the platform's current behavior rather than a stale copy.

<Info>
  Separately, an [MCP server for **managing** your MCP Manager workspace](/admin-api/overview) — creating servers, gateways, roles, and more from an agent — is now in **closed beta**. That admin MCP server is distinct from the docs MCP server described here: one operates your workspace, the other answers questions about the product.
</Info>

## The docs MCP server

The docs MCP server at `https://docs.mcpmanager.ai/mcp` is a standard remote MCP endpoint. Point any MCP-capable agent at it and the agent can read these docs in context while it works. It exposes:

* **Search** — finds relevant content across the site and returns snippets with titles and links, so the agent can locate the right page from a natural-language question.
* **Query docs filesystem** — navigates the docs as a virtual filesystem with shell-style commands (list, read, and search files), so the agent can read a specific page or grep across many, including the API reference.
* **The agent skill** — `skill.md` is exposed as a resource the agent can discover and load.

## Connect your coding agent directly

The fastest path: add the docs MCP server URL to whatever agent runtime your team uses. The endpoint is `https://docs.mcpmanager.ai/mcp`, it speaks streamable HTTP, and the public docs need no key. Nothing sits between the agent and the docs — for the governed alternative, see [Connect through your MCP Manager gateway](#connect-through-your-mcp-manager-gateway) below.

<Tabs>
  <Tab title="Claude Code">
    Run one command:

    ```bash terminal theme={null}
    claude mcp add --transport http mcp-manager-docs https://docs.mcpmanager.ai/mcp
    ```
  </Tab>

  <Tab title="Cursor">
    Add the server to your `mcp.json`:

    ```json mcp.json theme={null}
    {
      "mcpServers": {
        "mcp-manager-docs": {
          "url": "https://docs.mcpmanager.ai/mcp"
        }
      }
    }
    ```
  </Tab>

  <Tab title="VS Code">
    Create `.vscode/mcp.json`:

    ```json .vscode/mcp.json theme={null}
    {
      "servers": {
        "mcp-manager-docs": {
          "type": "http",
          "url": "https://docs.mcpmanager.ai/mcp"
        }
      }
    }
    ```
  </Tab>

  <Tab title="Claude.ai">
    In **Customize → Connectors**, choose **Add custom connector**, then enter a name and the URL `https://docs.mcpmanager.ai/mcp`.
  </Tab>
</Tabs>

## Connect through your MCP Manager gateway

Connecting directly points your agent at the public docs server with nothing in between. Registering the docs MCP server behind your own **MCP Manager** gateway gives the same access in governed form: every docs query flows through your gateway, so it is logged, your [gateway rules](/features/gateway-rules/overview) apply, and the whole team connects to one approved endpoint instead of ad-hoc URLs.

MCP Manager ships a shortcut for exactly this:

<Steps>
  <Step title="Open the shortcut from the support page">
    In MCP Manager, go to **Settings → Support** and select **Connect your agent to our docs MCP server**. You land on the **MCP Servers** page
    with the **Add Remote Server** panel already open and `https://docs.mcpmanager.ai/mcp` pre-filled.
  </Step>

  <Step title="Complete the add flow">
    Continue through the panel as you would for any remote server. The docs server is public and requires no key, so it connects without OAuth or
    header credentials.
  </Step>

  <Step title="Serve it from a gateway and connect your agent">
    Add the new server to a gateway, then point your agent at your gateway's endpoint using the same client instructions as above — your gateway
    URL replaces the public one. See [Connection Experience](/features/connection-experience) for what the end user sees.
  </Step>
</Steps>

<Tip>
  No shortcut required: you can register the docs server manually at any time — open **MCP Servers**, choose **Add**, pick a remote server, and
  paste `https://docs.mcpmanager.ai/mcp`. [Remote MCP Servers](/mcp-gateway-concepts/mcp-servers/remote) covers the full flow. Either path needs
  the **Basic server management** capability — see the [capabilities reference](/deployment/rbac-and-roles/capabilities).
</Tip>

## The agent skill

The docs MCP server lets an agent **read** the documentation; the **agent skill** teaches it how to **act** on the product to answer your questions.

<Steps>
  <Step title="Get the skill">
    The skill is published at `https://docs.mcpmanager.ai/skill.md`. The docs MCP server also exposes it as a resource, so a connected agent can
    discover it without a manual download.
  </Step>

  <Step title="Load it into your agent runtime">
    Drop `skill.md` into the agent runtime your team uses — for example, as a skill in Claude Code. The agent then has the operating manual in context
    whenever it works with MCP Manager.
  </Step>
</Steps>

## Further reading

<CardGroup cols={2}>
  <Card title="Remote MCP Servers" icon="cloud" href="/mcp-gateway-concepts/mcp-servers/remote">
    Register the docs MCP server — or any URL-based server — behind a gateway.
  </Card>

  <Card title="Connection Experience" icon="plug-circle-check" href="/features/connection-experience">
    What connecting to a governed gateway looks like for the end user.
  </Card>

  <Card title="Gateway Rules Overview" icon="shield-halved" href="/features/gateway-rules/overview">
    The rules an agent can read about, and that you can apply to docs traffic.
  </Card>

  <Card title="Introduction" icon="house" href="/get-started/introduction">
    What MCP Manager is and the problem it solves.
  </Card>
</CardGroup>

## External sources

<CardGroup cols={2}>
  <Card title="Mintlify: MCP server" icon="plug" href="https://www.mintlify.com/docs/ai/model-context-protocol">
    How the hosted docs MCP server, its tools, and the discovery document work.
  </Card>

  <Card title="Mintlify: llms.txt" icon="file-lines" href="https://www.mintlify.com/docs/ai/llmstxt">
    The llms.txt and llms-full.txt standard generated for AI ingestion.
  </Card>
</CardGroup>