---
title: "MCP for readers"
url: "/help/buuk/mcp-for-readers"
updated: "2026-10-22T11:13:50.620Z"
---
# MCP for readers

Every workspace can expose a public, read-only MCP server at `/api/public/mcp/<workspace-slug>`. It speaks the JSON-RPC protocol that Model Context Protocol tools already use, so external AI assistants can search your help center and answer from your documentation instead of their own imagination.

The endpoint needs no token and no allow-list. It is POST-only JSON-RPC served with open CORS: once you turn it on, any MCP client — Claude, ChatGPT, Cursor, or a custom agent you write — can point at the workspace URL and start calling tools.

## Turn it on

1. Open **Settings → General** in the dashboard.
2. Find the **Let AI tools search your docs** panel and switch it on. Owners and editors can change the toggle; other roles see it read-only.
3. Point your tool at `/api/public/mcp/<workspace-slug>`. The server answers `initialize`, `tools/list`, and `tools/call`.

> [!NOTE]
> The endpoint only serves while the help center is public. If the site is private, the toggle stays dormant until the help center is public again — nothing leaks through while it is paused.

## What tools can call

The server answers `tools/list` with seven read-only tools:

| Tool | Returns |
| --- | --- |
| `search_docs` | Published articles, guides, and FAQ entries matching a free-text query, with titles, slugs, excerpts, and URLs |
| `get_article` | One published article in full by slug or id — title, publish date, URL, and the body as markdown |
| `list_sections` | The workspace sections (categories) in display order |
| `list_recent_updates` | The most recently updated published articles, newest first |
| `list_api_specs` | Published OpenAPI specs with operation counts and versions |
| `search_api_reference` | Matching API reference operations by method, path, or summary |
| `get_api_operation` | One API operation as LLM-readable markdown — authentication, parameters, request body, responses |

Article URLs come back in the form `/help/<workspace-slug>/<slug>`, so an assistant can link readers straight to the page it quoted.

## What is exposed — and what is not

- Published public content only. Drafts and unpublished edits never leave the dashboard.
- Sections set to private visibility are excluded from every tool response — their articles cannot be searched or fetched.
- Hidden articles (direct-link only) and articles restricted to reader groups stay out as well.
- The surface mirrors what a crawler can reach on your public site — the same set listed in llms.txt.

> [!TIP]
> To preview exactly what an external tool will see, open the workspace’s `llms.txt` file. If a page appears there, it is on the MCP surface too; if it does not, external agents cannot reach it.

## Related

- The token-authenticated server for your own team: [MCP for authors](./mcp-for-authors).
- The crawlable surface this endpoint mirrors: [llms.txt & markdown endpoints](./llms-txt-and-markdown).
- Make the docs answer-ready in the first place: [Doc health and freshness](./doc-health-and-freshness).
- What readers get on the site itself: [Search and Ask AI for readers](./search-and-ask-ai).