---
title: Docs MCP
description: Search and read Orchestor documentation from your editor using MCP.
canonical_url: https://orchestor.io/docs/en/learn/docs-mcp
markdown_url: https://orchestor.io/docs/en/learn/docs-mcp.md
contentType: how-to
---

# Docs MCP

Orchestor provides a read-only MCP server for searching and retrieving public documentation. No account or API key is required.

**Server URL (Streamable HTTP)**

```text
https://orchestor.io/docs/api/mcp
```

## What it provides

- Use `docs_search` to find relevant public documentation.
- Use `docs_get_page` with a result's `path`, or pass its `resourceUri` as `uri`, to retrieve its Markdown content.
- Bring instructions and configuration examples into your agent's context while you work.

> **Note**
> 
> Docs MCP is documentation-only. Use the authenticated [Orchestor MCP](https://orchestor.io/docs/en/mcp.md) to read or change workspace data.

## Search, read, and cite

1. Call `docs_search` with a concise query. Set `locale` to `ja` or `en` to filter by language, and `limit` to request up to 20 results.
2. Pass a result's `path` to `docs_get_page` and read its Markdown content. You can also pass its `resourceUri` value as `uri`.
3. Answer using the page content and cite the returned `url` or the page's `canonical_url`.

Read the full page before making claims about a feature. Search snippets help you find pages; if the page does not establish an answer, say what remains unknown.

## Quickstart

Choose your editor and register the server.

### Codex

Add the server using the Codex CLI. The CLI and IDE extension share this configuration.

```bash
codex mcp add orchestorDocs --url https://orchestor.io/docs/api/mcp
codex mcp list
```

Alternatively, add this to `~/.codex/config.toml`:

```toml
[mcp_servers.orchestorDocs]
url = "https://orchestor.io/docs/api/mcp"
```

### VS Code

Add the server to your project's `.vscode/mcp.json`:

```json
{
  "servers": {
    "orchestorDocs": {
      "type": "http",
      "url": "https://orchestor.io/docs/api/mcp"
    }
  }
}
```

Open Copilot Chat, switch to Agent mode, and enable the server in the tools picker.

### Cursor

Add the server to `~/.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "orchestorDocs": {
      "url": "https://orchestor.io/docs/api/mcp"
    }
  }
}
```

Restart Cursor and confirm the connection in its MCP settings.

### Claude Code

Add the server from your project:

```bash
claude mcp add --transport http orchestorDocs https://orchestor.io/docs/api/mcp
claude mcp list
```

Use `--scope user` to make it available across your projects:

```bash
claude mcp add --transport http --scope user orchestorDocs https://orchestor.io/docs/api/mcp
```

Run `/mcp` in Claude Code to confirm the connection.

After setup, ask your agent:

```text
Search for "visibility" using Orchestor Docs MCP and retrieve the matching page.
Summarize the metric definition and instructions, and cite the page URL.
```

## Tell your agent to use the docs

Add this instruction to your project's `AGENTS.md` or the instruction file your agent reads:

```text
When working with Orchestor features, CLI commands, or settings, use orchestorDocs
and docs_search to find official documentation, then read the page with docs_get_page.
Cite the page URL in your answer. Do not infer specifications the page does not establish.
```

Without this instruction, explicitly ask the agent to use Docs MCP in your conversation. Set `locale: "en"` in `docs_search` to search English pages, or `locale: "ja"` for Japanese pages.

## Pair it with skills

[Orchestor skills](https://orchestor.io/docs/en/agent-resources/skills.md) guide command selection and workflows. Use Docs MCP to read the relevant specification, then follow the skill's instructions. Workspace operations require separate authentication.

If your environment cannot connect to MCP, use [Markdown and document discovery](https://orchestor.io/docs/en/agent-resources/markdown-access.md) to retrieve public documentation.

---

[Documentation index](https://orchestor.io/docs/llms.txt)