菜单
Query the official Strapi documentation through the strapi-docs MCP server (powered by Kapa). Use for any Strapi question — API syntax, configuration, features, plugins, upgrades, CLI. If the server is missing, instruct the user how to install it.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/strapi/skills --skill strapi-docs-mcp命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Run a structured, business-value-first product-planning interview that turns a fuzzy idea into a build-ready spec — BEFORE any code is written. Use this the moment someone is still figuring out WHAT to build and says things like "I have an idea for an app, help me think it through", "help me plan/scope/design my product", "where do I start?", "let's spec this out before I write code", or "turn this into a PRD". Covers any new app, site, SaaS, MVP, marketplace, or feature. Trigger on the planning intent alone — the user need NOT mention Strapi, a CMS, or any tech; a Strapi v5 + Strapi Cloud backend (overridable, with your choice of frontend and auth) is assumed by default. It nails value, users, and requirements before any tech decision, then produces six markdown files ending in a build spec you can hand to any coding agent (Claude Code, Cursor, etc.). Do NOT use once a spec or project exists and the user wants to scaffold, configure, migrate, add pages, wire auth, or debug — those are build tasks, not idea-s
Upgrade a Strapi application to a new version. ALWAYS reviews the relevant breaking changes first (via the strapi-docs MCP server, or by fetching the docs directly if the MCP is unavailable), then performs the upgrade using the official @strapi/upgrade tool. Use whenever the user wants to upgrade, update, or bump their Strapi version.
Create custom MCP capabilities (tools, prompts, resources) in a Strapi 5 plugin via the strapi.ai.mcp service. Use when adding a custom MCP tool/prompt/resource to Strapi, extending the Strapi MCP server.
基于 SOC 职业分类
正在显示 SKILL.md
| name | strapi-docs-mcp |
| description | Query the official Strapi documentation through the strapi-docs MCP server (powered by Kapa). Use for any Strapi question — API syntax, configuration, features, plugins, upgrades, CLI. If the server is missing, instruct the user how to install it. |
The strapi-docs MCP server (URL: https://strapi-docs.mcp.kapa.ai) exposes the full Strapi documentation (guides, API references, code examples). Prefer it over training data for Strapi answers, which may be outdated.
Canonical source: https://docs.strapi.io/cms/ai/docs-mcp-server
Check whether a strapi-docs MCP server / tool is connected in the current environment.
Call the strapi-docs MCP tools to answer Strapi questions. Pass the user's question directly; quote exact API names, config keys, and versions returned. Cite doc links in the answer.
Add a remote HTTP MCP server named: strapi-docs (URL https://strapi-docs.mcp.kapa.ai) to the host tool's MCP config, using its standard format. The server uses OAuth — the user completes an auth flow on first connection. Then have them reload/restart so it connects.
Per-tool config formats: https://docs.strapi.io/cms/ai/docs-mcp-server#connection-details
If the MCP server is unavailable and can't be installed, fall back to the public documentation content. No authentication is required for any of these. Prefer them in this order.
.md to any page URL)Any documentation page is available as flat Markdown by appending .md to its URL. All layout components (tabs, accordions, API blocks) are resolved to plain text, so nothing is hidden.
https://docs.strapi.io/cms/backend-customization/controllershttps://docs.strapi.io/cms/backend-customization/controllers.md.md to any https://docs.strapi.io/<page-path>This is the same content the docs site's Copy Markdown button uses.
These follow the llms.txt convention and are the most agent-friendly source: content is flattened to plain Markdown, so nothing is hidden inside tabs or accordions.
| File | URL | Use for |
|---|---|---|
| Index | https://docs.strapi.io/llms.txt | Discover every page: a link-rich list of all pages with one-line summaries. |
| Full content | https://docs.strapi.io/llms-full.txt | The entire documentation in a single file. Fetch once, then search/grep in it. |
| Code only | https://docs.strapi.io/llms-code.txt | All code examples, grouped by page. |
Constructing a page URL from llms.txt: entries are protocol-relative paths like //cms/backend-customization/controllers. Prepend the docs origin to get the live page as follows:
//cms/backend-customization/controllers becomes https://docs.strapi.io/cms/backend-customization/controllers
Each page is a .md/.mdx file in strapi/documentation. Use this only if docs.strapi.io itself is unreachable. Build the raw URL from the page path:
/cms/backend-customization/controllershttps://raw.githubusercontent.com/strapi/documentation/main/docusaurus/docs/cms/backend-customization/controllers.mdhttps://raw.githubusercontent.com/strapi/documentation/main/docusaurus/docs/<page-path>.md
where <page-path> is the page URL path (drop the leading /). Some pages use .mdx — if .md returns 404, retry with .mdx.Fetch the page directly, e.g. https://docs.strapi.io/cms/backend-customization/controllers, and extract the content. Least reliable: some content lives in tabs/accordions and may be missed. Prefer sources 1 to 3 whenever possible.