Skip to main content

​
Built-in Mintlify LLM Surfaces

Mintlify already exposes LLM-friendly formats: That means you do not need a custom parser just to support copy-to-LLM workflows.

​
Grounding Docs in Code

The reliability requirement is drift control: docs should be generated from source, not hand-maintained. For OrgX cloud MCP tools:
For OpenClaw plugin MCP tools (cross-repo generation):
This command reads:
  • Code/orgx-openclaw-plugin/src/tools/core-tools.ts
  • Code/orgx-openclaw-plugin/src/mcp-http-handler.ts
and regenerates:
  • docs/mintlify/generated/openclaw-plugin-tool-catalog.json
  • docs/mintlify/api/openclaw-plugin-mcp-tools.mdx
  1. Regenerate catalogs before each docs release.
  2. Commit generated outputs with timestamps.
  3. Run broken-link checks:
  4. Spot-check .md variants for key pages (for example /api/mcp-tools.md).
  5. Verify llms.txt and llms-full.txt include newly added pages after deploy.

​
Copy-to-LLM for Every Page

For end users, the simplest “copy to LLM” path is:
  • open the page in docs
  • append .md to the URL
  • copy the markdown output
Example:
  • Docs page: /api/openclaw-plugin-mcp-tools
  • LLM-ready variant: /api/openclaw-plugin-mcp-tools.md