Get Started
PreviousNext

MCP Capabilities

Stable capability map for coding agents consuming this documentation.

What It Does

This page defines stable capability-to-doc mappings for MCP ingestion and agent retrieval.

When To Use

  • Building an MCP server on top of this docs website.
  • Prompting coding agents to navigate the kit quickly.

Prerequisites

  • Access to /docs/* and /llms.mdx/* endpoints.
  • Access to /mcp-index.json generated capability endpoint.

How To Use

Use this map as the first retrieval layer.

CapabilityPrimary pageRelated pages
analytics_integration/docs/web/features/analytics
app_configuration/docs/web/configuration
ask_ai_ui/docs/web/features/cms/components/ask-ai
auth_mobile_integration/docs/mobile/features/authentication/integration
auth_mobile_settings_ui/docs/mobile/features/authentication/user-settings
auth_mobile_setup/docs/mobile/features/authentication
auth_mobile_user_access/docs/mobile/features/authentication/retrieve-user
auth_settings_ui/docs/web/features/authentication/user-settings
auth_user_access/docs/web/features/authentication/retrieve-user
auth_web_integration/docs/web/features/authentication/integration
auth_web_setup/docs/web/features/authentication
billing_core/docs/web/features/billing
billing_integration/docs/web/features/billing/integration
billing_pricing_ui/docs/web/features/billing/pricing
billing_settings_ui/docs/web/features/billing/user-settings
bootstrap_project/docs/web
captcha_protection/docs/web/features/authentication/_captcha
cms_architecture/docs/web/features/cms
database_workflow/docs/database
docs_platform/docs/web/features/documentation
email_provider_config/docs/web/features/emails/providers
email_sending/docs/web/features/emails
email_template_rendering/docs/web/features/emails/templates
fumadocs_integration/docs/web/features/cms/fumadocs
google_analytics_provider/docs/web/features/analytics/google-analytics
i18n_mobile_setup/docs/mobile/features/translations
i18n_usage_patterns/docs/web/features/translations/usage
i18n_web_setup/docs/web/features/translations
keybindings_persistence/docs/web/features/keybindings/storage
keybindings_system/docs/web/features/keybindings
language_selector_ui/docs/web/features/translations/language-selector
mcp_doc_index/docs/web/mcp-capabilities
mcp_server_integration/docs/mcp-server
mobile_bootstrap/docs/mobile
monitoring_setup/docs/web/features/monitoring
notion_content_backend/docs/web/features/cms/notion
notion_markdown_export/docs/web/features/cms/notion/llms
notion_search/docs/web/features/cms/notion/search
onboarding_flow/docs/web/features/onboarding
onboarding_mobile_flow/docs/mobile/features/onboarding
product_overview/docs/benefits
production_deployment/docs/web/deployment
project_generation_and_refactor/docs/cli
repo_navigation/docs/structure
repo_task_execution/docs/scripts
roadmap_content/docs/web/features/roadmap
scroll_to_top_ui/docs/web/features/cms/components/scroll-to-top
settings_api_fullstack/docs/web/features/settings
settings_architecture/docs/settings-package-interest
settings_mobile_ui/docs/mobile/features/settings
toc_ui/docs/web/features/cms/components/toc
umami_provider/docs/web/features/analytics/umami

MCP Context

capability: mcp_doc_index
entrypoints:
  - /docs/web/mcp-capabilities
  - /llms.mdx/[...slug]
  - /mcp-index.json
inputs:
  - capability_id
outputs:
  - doc_urls_for_retrieval
constraints:
  - capability ids should remain stable for MCP clients
side_effects:
  - none

Agent Recipe

  1. Resolve user intent to one capability id.
  2. Retrieve primary page first, then secondary pages.
  3. If code edits are requested, map docs guidance to real paths in apps/* and kit/*.

Troubleshooting

  • If a URL is stale, update this page first and keep capability ids unchanged.
  • If retrieval quality is low, narrow capability ids instead of adding broad pages.

How is this guide?

Last updated on 3/23/2026