Make published docs directly usable by agents
dubstack gives documentation sites public read-only MCP access so compatible agents can query docs without scraping or guessing.
Key points
Public docs can expose MCP tools for search and read-only filesystem-style access.
Agents can retrieve authoritative docs content with URLs and page paths.
MCP access is separate from authenticated authoring tools for customers.
Read-only public access protects customer docs while improving agent usability.
Public MCP for documentation readers
A public docs site should be useful to humans and agents. MCP gives agents a structured way to search and read published documentation.
- -Search tools return relevant pages and snippets.
- -Read tools expose published docs files without write access.
- -Agents can cite the same public URLs that human users can open.
Clear boundary from authoring access
Public MCP is for reading published docs. Authenticated authoring and workflow actions belong to customer-owned dashboard and agent surfaces.
- -Public readers get search and read-only access.
- -Site owners control writing through authenticated dashboard and Git workflows.
- -This split keeps public discovery useful without exposing privileged operations.
Questions
Is public MCP read-only?
Yes. Public documentation MCP is intended for search and reading published docs, not editing customer content.
Why expose docs through MCP?
MCP gives agents a structured interface to retrieve current docs content instead of relying only on general web search or stale model memory.