Skip to main content
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

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.
Separately, an MCP server for managing your MCP Manager workspace — 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.

​
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 below.
Run one command:
terminal

​
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 apply, and the whole team connects to one approved endpoint instead of ad-hoc URLs. MCP Manager ships a shortcut for exactly this:
1

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.
2

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.
3

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 for what the end user sees.
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 covers the full flow. Either path needs the Basic server management capability — see the capabilities reference.

​
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.
1

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.
2

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.

​
Further reading

Remote MCP Servers

Register the docs MCP server — or any URL-based server — behind a gateway.

Connection Experience

What connecting to a governed gateway looks like for the end user.

Gateway Rules Overview

The rules an agent can read about, and that you can apply to docs traffic.

Introduction

What MCP Manager is and the problem it solves.

​
External sources

Mintlify: MCP server

How the hosted docs MCP server, its tools, and the discovery document work.

Mintlify: llms.txt

The llms.txt and llms-full.txt standard generated for AI ingestion.