strapi-mcp
Provides AI-powered content management for Strapi CMS, including tools for CRUD operations on content types, media management, publication lifecycle, internationalization, search, and bulk actions.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@strapi-mcp list published articles"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Strapi MCP Server
AI-powered content management for Strapi CMS via Model Context Protocol.
Features
Connect any MCP-compatible AI assistant (Claude, Cursor, etc.) to your Strapi CMS. Manage content, media, locales, and more through natural language.
20 Tools across 8 categories
Category | Tools | Description |
Schema (3) |
| Discover and inspect content models |
Content (5) |
| Full CRUD for any content type |
Media (3) |
| Upload, browse, and manage media library |
Publish (3) |
| Control publication lifecycle |
i18n (2) |
| Internationalization support |
Search (2) |
| Full-text search and counting |
Bulk (1) |
| Batch create, update, or delete |
System (1) |
| Server info and version detection |
Additional MCP capabilities
3 Prompts:
manage_content,content_migration,setup_guide-- guided workflows for common tasks1 Resource:
strapi://help-- comprehensive usage guide with examples
Related MCP server: Strapi MCP Server
Quick Start
Install the server:
pip install strapi-mcpConfigure your Strapi connection:
export STRAPI_BASE_URL="http://localhost:1337" export STRAPI_API_TOKEN="your-strapi-api-token"Connect from your MCP client (see Client Configuration below).
Installation
Using pip
pip install strapi-mcpUsing uvx (no install required)
uvx strapi-mcpFrom source
git clone https://github.com/alexzimmermann/strapi-mcp.git
cd strapi-mcp
pip install -e .Configuration
All settings are configured via environment variables with the STRAPI_ prefix:
Variable | Default | Description |
|
| URL of your Strapi instance |
| (empty) | API token for authentication. Create in Strapi Admin > Settings > API Tokens. |
|
| Strapi version: |
|
| HTTP request timeout in seconds |
|
| Maximum entries per page (1-100) |
You can also place these in a .env file in your working directory.
Creating a Strapi API Token
Open your Strapi Admin panel (e.g.,
http://localhost:1337/admin)Navigate to Settings > API Tokens
Click Create new API Token
Set Token type to Full Access (or customize permissions)
Copy the generated token and set it as
STRAPI_API_TOKEN
Client Configuration
Claude Desktop
Add to your Claude Desktop config file (claude_desktop_config.json):
{
"mcpServers": {
"strapi": {
"command": "uvx",
"args": ["strapi-mcp"],
"env": {
"STRAPI_BASE_URL": "http://localhost:1337",
"STRAPI_API_TOKEN": "your-strapi-api-token"
}
}
}
}Cursor
Add to your Cursor MCP config:
{
"mcpServers": {
"strapi": {
"command": "uvx",
"args": ["strapi-mcp"],
"env": {
"STRAPI_BASE_URL": "http://localhost:1337",
"STRAPI_API_TOKEN": "your-strapi-api-token"
}
}
}
}Smithery
This server is available on Smithery. Install directly from the Smithery registry or configure manually using the smithery.yaml included in this repository.
Available Tools
Tool | Description |
| List all available content types in the Strapi instance |
| Get the full field schema for a specific content type |
| List all reusable components and their schemas |
| List entries with filtering, sorting, pagination, and population |
| Get a single entry by ID (or documentId in v5) |
| Create a new content entry with field data |
| Update an existing entry by ID |
| Delete an entry by ID |
| Upload a file to the media library (URL or base64) |
| Browse the media library with pagination |
| Delete a file from the media library |
| Publish a draft entry to make it publicly available |
| Revert a published entry to draft status |
| Discard unsaved draft changes (Strapi v5 only) |
| List all configured locales for i18n |
| Get an entry in a specific locale |
| Full-text search across entries of a content type |
| Count entries matching optional filter criteria |
| Perform bulk create, update, or delete operations |
| Get Strapi server info, version, and connection status |
Strapi Version Support
This server supports both Strapi v4 and Strapi v5 with automatic version detection.
Auto-detection
When STRAPI_API_VERSION is set to auto (the default), the server detects your Strapi version at startup by:
Fetching a content type entry and inspecting its response format
Checking the admin information endpoint for a version string
Defaulting to v5 if detection is inconclusive
Key differences handled automatically
Feature | Strapi v4 | Strapi v5 |
Entry format | Nested | Flat with |
Entry identifier | Numeric | String |
Publication status |
|
|
Draft discard | Not available |
|
You can force a specific version by setting STRAPI_API_VERSION=v4 or STRAPI_API_VERSION=v5.
Development
Setup
git clone https://github.com/alexzimmermann/strapi-mcp.git
cd strapi-mcp
python -m venv .venv
source .venv/bin/activate # or .venv\Scripts\activate on Windows
pip install -e ".[dev]"Running tests
pytestRunning with coverage
pytest --cov=strapi_mcp --cov-report=term-missingCode style
ruff check .
ruff format .License
MIT License. See LICENSE for details.
Available Tools
20 toolsbulk_actionA
Execute a bulk operation (create, update, delete, publish, or unpublish) on multiple content entries. Processes each entry sequentially with per-entry error handling so individual failures do not abort the entire batch. Returns a detailed summary showing successes, failures, and error messages for each entry. Use this for batch imports, migrations, or mass status changes.
Inputs: action (required), entries (required), content_type (required). Returns: result
count_entriesARead-only
Count the total number of entries in a content type, optionally filtered by criteria. Makes a lightweight API call that only requests pagination metadata to get the total count efficiently. Use this to understand dataset sizes before bulk operations or to verify migration completeness.
Inputs: content_type (required), locale, status, filters. Returns: result
create_entryA
Create a new content entry in the specified Strapi content type. Accepts a JSON string with field values that match the content type schema. Use get_content_type_schema first to understand which fields are required and their expected types before calling this tool.
Inputs: data (required), content_type (required), locale, status. Returns: result
delete_entryADestructive
Permanently delete a content entry by its ID from the specified content type. This action is irreversible and will remove the entry and its associated data. Use get_entry first to verify you are deleting the correct entry. If a locale is specified, only that localization is removed.
Inputs: entry_id (required), content_type (required), locale. Returns: result
delete_mediaADestructive
Permanently delete a file from the Strapi media library by its ID. This removes the file from storage and breaks any references to it in content entries. Use list_media first to find the correct file ID before deleting. This action cannot be undone.
Inputs: file_id (required). Returns: result
discard_draftADestructive
Discard unsaved draft changes on a content entry, reverting to the last published version. This is only available on Strapi v5 which has a separate draft layer. On Strapi v4, this operation is not supported and will return an error. Use this when you want to abandon draft edits without affecting the currently published version.
Inputs: entry_id (required), content_type (required), locale. Returns: result
get_componentsARead-only
List all reusable components defined in the Strapi instance. Components are shared field groups that can be embedded in multiple content types (e.g., SEO metadata, address blocks). Use this to understand available components before referencing them in content type schemas or entry data.
Inputs: no named parameters. Returns: result
get_content_type_schemaARead-only
Retrieve the detailed field schema for a specific Strapi content type. Returns all field definitions including types, required status, and relations, formatted as a readable list. Use this before creating or updating entries to understand the expected data structure and required fields.
Inputs: content_type (required). Returns: result
get_entryARead-only
Retrieve a single content entry by its ID with full field and relation data. Returns the complete entry including all populated relations and metadata fields. Use this when you need the full details of a specific entry after finding it via list_entries or search_entries.
Inputs: entry_id (required), content_type (required), locale, populate. Returns: result
get_localized_entryARead-only
Retrieve a specific localized version of a content entry by its ID and locale code. Returns the full entry data in the requested language, including all populated relations. Use list_locales first to see available locale codes, then use this to fetch content in a specific language for comparison or translation workflows.
Inputs: locale (required), entry_id (required), content_type (required), populate. Returns: result
get_strapi_infoARead-only
Retrieve comprehensive information about the connected Strapi instance including version, plugins, and content types. Performs multiple API calls to detect the Strapi version (v4 or v5), count available content types, list installed plugins, and check configured locales. Use this as the first tool call when connecting to a new Strapi instance to understand its configuration and capabilities.
Inputs: no named parameters. Returns: result
list_content_typesARead-only
List all user-defined content types registered in the Strapi instance. Fetches content types from the Content-Type Builder API and filters to only include those in the 'api::' namespace (i.e., user-created types). Use this as a first step to discover what content is available before querying entries.
Inputs: no named parameters. Returns: result
list_entriesARead-only
List content entries from a Strapi content type with full pagination, sorting, and filtering support. Returns entries formatted as a readable markdown list with metadata and pagination info. Use this to browse and explore content, applying filters and sort orders as needed. Call list_content_types first if you are unsure which content types are available.
Inputs: content_type (required), page, sort, fields, +5 more. Returns: result
list_localesARead-only
List all locales configured in the Strapi i18n plugin with their codes and display names. Returns each locale's code, display name, and whether it is the default locale. Use this to discover available languages before creating or querying localized content entries.
Inputs: no named parameters. Returns: result
list_mediaARead-only
List files in the Strapi media library with pagination support. Returns file details including name, URL, type, dimensions, and metadata for each media asset. Use this to browse available files before linking them to content entries or to find files for deletion.
Inputs: page, page_size. Returns: result
publish_entryA
Publish a draft content entry to make it publicly visible via the Strapi API. On Strapi v5, uses the dedicated publish action endpoint; on v4, sets the publishedAt timestamp. Use list_entries with status='draft' to find unpublished entries that need publishing.
Inputs: entry_id (required), content_type (required), locale. Returns: result
search_entriesARead-only
Search for content entries matching a text query within a specific content type. Uses case-insensitive containment filters ($containsi) on string fields to find matching entries. Specify search_fields to narrow the search to specific fields, or leave it empty to search common text fields like title, name, and description.
Inputs: query (required), content_type (required), page, page_size, +1 more. Returns: result
unpublish_entryA
Unpublish a live content entry, reverting it to draft status so it is no longer publicly visible. On Strapi v5, uses the dedicated unpublish action endpoint; on v4, sets publishedAt to null. The entry data is preserved and can be re-published later with publish_entry.
Inputs: entry_id (required), content_type (required), locale. Returns: result
update_entryA
Update an existing content entry by its ID with partial or full field data. Only the fields included in the data JSON will be modified; other fields remain unchanged. Use get_entry first to see the current values, then provide only the fields you want to change.
Inputs: data (required), entry_id (required), content_type (required), locale. Returns: result
upload_mediaA
Upload a file to the Strapi media library from a URL or base64-encoded data. Supports images, documents, videos, and any file type allowed by Strapi. Provide either a public file_url or base64 content along with a descriptive file name. The uploaded file can then be linked to content entries via relation fields.
Inputs: caption, alt_text, file_url, file_name, +1 more. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 20 tools
Every tool targets a distinct aspect of Strapi CMS: content entries, media, locales, schemas, bulk operations, etc. No two tools have overlapping purposes; even similar ones like get_entry and get_localized_entry are clearly differentiated by locale.
All tool names follow a consistent verb_noun pattern using lowercase snake_case (e.g., create_entry, delete_media, list_content_types). This predictability makes it easy for an agent to infer functionality from names.
With 20 tools, the server covers the full spectrum of Strapi operations—CRUD, media management, localization, schema inspection, bulk actions—without being overly numerous or sparse. Each tool serves a clear purpose.
The tool surface is comprehensive: full lifecycle for entries (create, read, update, delete, publish, unpublish, draft discard), media (upload, list, delete), locale support, schema discovery, and even bulk operations. No obvious gaps for typical CMS workflows.
Maintenance
Related MCP Connectors
Manage SRG+ hubs, channels, content, assets, users, and workspaces from any MCP-aware AI agent.
Connect e-commerce and marketing data to AI assistants via MCP.
Connect any AI agent to 1,000+ apps and 27,000+ actions through one remote MCP server (OAuth).
Manage WordPress blogs and WooCommerce shops from Claude, ChatGPT, Cursor and other MCP apps.
Related MCP Servers
- AlicenseAqualityBmaintenanceA Model Context Protocol server that enables AI assistants to interact with Strapi CMS instances through a standardized interface, supporting content types and REST API operations.569 npm75MIT
- AlicenseNot gradedqualityDmaintenanceProvides access to Strapi CMS content through the MCP protocol, allowing users to create, read, update, and delete content entries via Claude.118 npm25MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Strapi CMS instances through REST API operations. Supports content management, media uploads, schema introspection, and multiple server configurations with JWT authentication.34 npmMIT
- AlicenseAqualityDmaintenanceMCP server for Strapi CMS content and media management.1518 npmMIT