Learn

​
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)

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.

Docs MCP is documentation-only. Use the authenticated Orchestor MCP 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.

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

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

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

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

After setup, ask your agent:

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:

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 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 to retrieve public documentation.