MCP100 Assessment

Editorial verdict

Promising content-platform integration, but it remains on the Shortlist until API-token scope, content mutations, deployment differences, sensitive data handling, and independent usability are more completely reviewed.

Reviewed July 30, 2026

Task Fit

Mapped

Specialized workflows

Trust

Status warning

mcp_relevance; documentation; maintenance_source_health; client_coverage; tool_contract; install_supply_chain; advisory_freshness; adoption_evidence_presence; resource_type_requirements

Maintenance

Date unavailable

No dated repository or package update is currently stored.

Popularity

Signals unavailable

No independently comparable adoption metric is currently stored.

Best for

Self-hosted CMS content and development workflows.

Not ideal for

Production use before the documented maturity gaps are resolved

Avoid if

The connected identity is broader than the task requires
Tool calls cannot be reviewed before consequential mutations

Trade-offs

The built-in implementation is newly released and explicitly Beta.

Evidence scope

Evidence

Current source snapshot

Popularity

No MCP-specific repository metric is stored

Built-in Strapi MCP · no comparable MCP-specific usage metric

Strapi MCP is delivered as a Strapi product capability; broader Strapi package/product adoption is not a comparable MCP-specific metric.

Stars observation date unavailable · Downloads observed September 8, 2026

No exact public repository is documented.

Strapi MCP is delivered as a Strapi product capability; broader Strapi package/product adoption is not a comparable MCP-specific metric.

Maintenance

Publisher activity observed July 30, 2026

Current source snapshot

Trust review

Source relationship: First-party MCP

Reviewed July 30, 2026

Sources

Publisher article ↗

Evidence-backed setup

Install & Agents

Choose your MCP client. A client connects to the MCP server; the language model is selected inside that client. Only stored, source-backed configurations are shown.

Claude Code

Local stdio

MCP100 logic checked

claude mcp add strapi-mcp -- npx "-y" "mcp-remote" "https://YOUR_STRAPI_HOST/mcp" "--header" "Authorization: Bearer YOUR_STRAPI_ADMIN_TOKEN"

The publisher connection details were combined with this client's official MCP transport configuration; installation was not executed by MCP100.

Verify safely: Restart Claude Code, confirm strapi-mcp tools are listed, and perform one read-only test with non-sensitive data.

Uninstall and revoke

Remove strapi-mcp from Claude Code, restart the client, remove any separately installed package, and revoke dedicated credentials if used.

Evidence & methodology

Publisher-documented setup is not the same as MCP100 execution testing. “MCP100 logic checked” means the stored configuration shape was reviewed, not that third-party MCP software was run.

Evidence checked 2026-08-12

Evidence 1 ↗Evidence 2 ↗

Capability

What it does

Expose built-in Strapi content-management capabilities through MCP.

Content & KnowledgeMedia & MarketingSoftware & Technology

Representative uses

Self-hosted CMS content and development workflows.

Important limits

Production use before the documented maturity gaps are resolved

ToolsDocumented capabilitiesView tools

Collection-type CRUD
Create, read, update, delete, and publish collection-type entries generated from the current Strapi content schema.
Single-type read/write/delete
Read, update, or remove single-type content generated from the current Strapi schema.
Draft & Publish operations
Manage draft, publish, and unpublish state when Draft & Publish is enabled for the relevant content type.
Custom plugin MCP tools
Expose additional project-specific MCP tools contributed by Strapi plugins.

Each Collection Type can generate up to 8 tools and each Single Type up to 6; actual tools depend on the project's schemas, Draft & Publish settings, admin-token permissions and plugin extensions.

Source: Official documentation

Context Footprint

Varies by configuration

Estimated token footprint of the MCP tool schemas exposed to the agent.

Product-level Context Footprint varies with the actually exposed tool surface.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: The built-in server follows Strapi authentication and API-token controls.
Permissions: Strapi roles, API tokens, content-type permissions, and deployment configuration govern access.
Data handling: Authorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive content & knowledge information.
Cost: The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply.
Risk and cautions: The built-in implementation is newly released and explicitly Beta. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review.

Related reviewed MCPs

Other options

Contentful MCP Server

MCP100 Recommended

Connect compatible AI clients to Contentful's documented MCP capabilities.

Choose this instead if

Choose Contentful MCP Server instead if connect compatible AI clients to Contentful's documented MCP capabilities.

Recommended after reviewed 2026-09-25 admission dossier: current_patched_first_party_server_all_selected_gates_pass.

Compare with Strapi MCP View Contentful MCP Server details

sanity

MCP100 Recommended

Manage authorized Sanity schemas, content, datasets, releases, queries, and images.

Choose this instead if

Choose sanity instead if structured-content development and editorial operations in Sanity.

Manage authorized Sanity schemas, content, datasets, releases, queries, and images.

Compare with Strapi MCP View sanity details

Playwright MCP

MCP100 Recommended

Let AI clients inspect and automate web browsers with Playwright.

Choose this instead if

Choose Playwright MCP instead if inspecting and testing web interfaces through accessibility snapshots.

Let AI clients inspect and automate web browsers with Playwright.

Compare with Strapi MCP View Playwright MCP details

Read publisher documentation

Publisher documentation

MCP100 source-backed summary

A concise MCP100 summary built from the reviewed publisher sources. It is not a publisher README; use the original link for the latest full documentation.

View original documentation ↗

Strapi MCP

Expose built-in Strapi content-management capabilities through MCP.

What it can help with

Self-hosted CMS content and development workflows.

Important limits

Production use before the documented maturity gaps are resolved

Loading optional publisher documentation…

FAQ

What can Strapi MCP do?

Expose built-in Strapi content-management capabilities through MCP.

What determines Strapi MCP's access?

Strapi's built-in MCP generates tools from the current project's content-type schemas. The available CRUD and Draft & Publish actions depend on the project's schemas, admin-token permissions, feature settings, and any plugin-provided MCP tools, so access varies by Strapi project rather than following one fixed permission set.

Does Strapi MCP work with Codex?

Yes. MCP100 reviewed an evidence-backed setup for Codex, but has not independently verified it with a live runtime test.

How does Strapi MCP authenticate?

The built-in server follows Strapi authentication and API-token controls.

Is Strapi MCP ready for production content operations?

The built-in implementation is newly released and explicitly Beta. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review.

Is this an official MCP?

ecosystem:strapi is listed as First-party MCP in MCP100’s current evidence.

Current official resources:

Publisher documentation ↗