Documentation

What It Does

The docs app (apps/creatorem) uses Fumadocs with MDX content under content/docs and exposes per-page LLM text endpoints.

When To Use

• Customizing docs architecture.
• Preparing docs for MCP retrieval.

Prerequisites

• Understand Fumadocs source config and docs route setup.

How To Use

Core pieces:

• source.config.ts defines docs source + frontmatter schema.
• lib/fumadocs/source.ts loads docs tree under /docs.
• app/(docs)/docs/[...slug]/page.tsx renders docs pages.
• app/llms.mdx/[...slug]/route.ts exposes page-level LLM text.
• app/mcp-index.json/route.ts exposes generated capability index for MCP consumers.
• scripts/generate-mcp-index.mts and scripts/check-mcp-contract.mts generate and validate machine-readable contracts.

For MCP readiness, keep page structure predictable and include machine-readable context blocks.

MCP Context

Copy to Clipboardcapability: docs_platform
entrypoints:
  - apps/creatorem/source.config.ts
  - apps/creatorem/content/docs/
  - apps/creatorem/app/llms.mdx/[...slug]/route.ts
  - apps/creatorem/app/mcp-index.json/route.ts
inputs:
  - mdx_docs_content
outputs:
  - rendered_docs_and_llm_text_endpoints
  - generated_mcp_capability_index
constraints:
  - docs tree and metadata must stay coherent
side_effects:
  - static docs generation

Agent Recipe

1. Update docs content and meta files together.
2. Validate docs routes and LLM route output.
3. Keep docs section contract stable for MCP consumers.

Troubleshooting

• Broken side navigation usually comes from invalid meta.json references.
• Broken LLM page output usually means unresolved docs slug.

Related

• MCP Capabilities
• Fumadocs