Atmos Pro's MCP server now exposes public documentation as a first-class tool surface. Your agent can search by topic, browse the docs index, and fetch exact pages as clean Markdown from the same MCP connection it already uses for workspace data.
That gives agents a simple advantage: they can read the product docs first, then inspect your live workspace with the right context. Setup, configuration, troubleshooting, and concept questions all start from current Atmos Pro documentation instead of a cold prompt.
The new docs path is optimized for agent context windows:
Search first. search_documentation returns the most relevant sections for a topic.
Markdown first. Pages are reduced to headings, prose, links, tables, and code blocks, so agents spend tokens on useful instructions.
Precise follow-up. get_documentation_page can fetch one page or one section when the agent needs exact setup steps.
Portable access. Public .md endpoints, /docs/sitemap.md, and /docs/llms.txt make the same docs useful outside MCP too.
In practice, your agent can move quickly through common questions like:
How do I install the MCP server?
How should drift detection be configured?
What permissions does a workflow need?
Why is a workflow dispatch failing?
The MCP server now tells agents to search documentation before inspecting live workspace state for setup, concept, and troubleshooting questions. That keeps investigations grounded in the current product behavior, then lets the agent move into live data only when it needs workspace-specific facts.
The result is a tighter loop: read the docs, inspect the workspace, explain the fix, and keep going.
|