AI and MCP
LaunchLab Docs publishes machine-readable versions of the same documentation that users see.
Text endpoints
When the docs run at https://example.com/docs, an agent can use:
| Resource | Path |
|---|---|
| Page as Markdown | /docs/markdown/<page-path>.md |
| Page index | /docs/llms.txt |
| Complete documentation | /docs/llms-full.txt |
| MCP server | /docs/api/mcp |
Use the current LaunchLab origin for these paths.
MCP tools
The Vocs MCP server exposes tools to:
- list documentation pages;
- read one page;
- search across the docs.
The MCP endpoint is part of the Vocs server runtime. A production router must send both /docs/* pages and /docs/api/mcp to that runtime. A static file-only host cannot provide the MCP endpoint.
Vocs also uses helper routes for generated Markdown, MCP session messages, and social images. The same-origin router must send /assets/md/*, /api/mcp/*, and /api/og* to the docs runtime. LaunchLab provides /docs/markdown/* and /docs/llms*.txt as stable public aliases.
Safety rule for agents
Treat proposals, examples, and prerequisites as informational, not as active features. Never infer a token, reward, contract address, or withdrawal tool that these docs do not explicitly publish.