An MCP server for Strapi CMS, providing access to content types and entries through the Model Context Protocol.
This MCP server integrates with any Strapi CMS instance to provide:
- Access to Strapi content types as resources
- Tools to create and update content types in Strapi
- Tools to manage content entries (create, read, update, delete)
- Support for Strapi in development mode
It's recommended to use a .env file in the project root to store your credentials.
STRAPI_URL: The URL of your Strapi instance (default:http://localhost:1337)STRAPI_ADMIN_EMAIL: The email address for a Strapi admin user (Recommended for full functionality, especially schema access).STRAPI_ADMIN_PASSWORD: The password for the Strapi admin user (Recommended).STRAPI_API_TOKEN: (Optional Fallback) An API token. Can be used if admin credentials are not provided, but may have limited permissions.STRAPI_DEV_MODE: Set to"true"to enable development mode features (defaults tofalse).
Example .env file:
STRAPI_URL=http://localhost:1337
STRAPI_ADMIN_EMAIL=your_admin_email@example.com
STRAPI_ADMIN_PASSWORD=your_admin_password
# STRAPI_API_TOKEN=your_api_token_here # OptionalImportant: Add .env to your .gitignore file to avoid committing credentials.
npm install strapi-mcpRecommended Method (using .env file):
Make sure you have built the project (npm run build). Then run the server using Node.js v20.6.0+ with the --env-file flag:
node --env-file=.env build/index.jsAlternative (using environment variables directly):
export STRAPI_URL=http://localhost:1337
export STRAPI_ADMIN_EMAIL=your_admin_email@example.com
export STRAPI_ADMIN_PASSWORD=your_admin_password
# export STRAPI_API_TOKEN=your-api-token # Optional fallback
export STRAPI_DEV_MODE=true # optional
# Run the globally installed package (if installed via npm install -g)
strapi-mcp
# Or run the local build directly
node build/index.js- List and read content types
- Get, create, update, and delete entries
- Upload media files
- Connect and disconnect relations
- Get content type schemas
- Added
create_content_typetool: Allows creating new content types via the Content-Type Builder API (requires admin credentials). - Prioritized Admin Credentials: Updated logic to prefer admin email/password for fetching content types and schemas, improving reliability.
- Updated Documentation: Clarified authentication methods and recommended running procedures.
- Improved content type discovery with multiple fallback methods
- Added more robust error handling and logging
- Enhanced schema inference for content types
- Improved error handling with more specific error codes
- Added
ResourceNotFoundandAccessDeniederror codes - Better error messages for common API errors
- Initial public release
MIT
An MCP server for your Strapi CMS
This is a TypeScript-based MCP server that integrates with Strapi CMS. It provides access to Strapi content types and entries through the MCP protocol, allowing you to:
- Access Strapi content types as resources
- Create, read, update, and delete content entries
- Manage your Strapi content through MCP tools
- List and access content types via
strapi://content-type/URIs - Each content type exposes its entries as JSON
- Application/JSON mime type for structured content access
list_content_types- List all available content types in Strapiget_entries- Get entries for a specific content type with optional filtering, pagination, sorting, and population of relationsget_entry- Get a specific entry by IDcreate_entry- Create a new entry for a content typeupdate_entry- Update an existing entrydelete_entry- Delete an entryupload_media- Upload a media file to Strapiget_content_type_schema- Get the schema (fields, types, relations) for a specific content type.connect_relation- Connect related entries to an entry's relation field.disconnect_relation- Disconnect related entries from an entry's relation field.create_content_type- Create a new content type using the Content-Type Builder API (Requires Admin privileges).
The get_entries tool supports advanced query options:
{
"contentType": "api::article.article",
"filters": {
"title": {
"$contains": "hello"
}
},
"pagination": {
"page": 1,
"pageSize": 10
},
"sort": ["title:asc", "createdAt:desc"],
"populate": ["author", "categories"]
}Resources can be accessed with various URI formats:
strapi://content-type/api::article.article- Get all articlesstrapi://content-type/api::article.article/1- Get article with ID 1strapi://content-type/api::article.article?filters={"title":{"$contains":"hello"}}- Get filtered articles
Install dependencies:
npm installBuild the server:
npm run buildFor development with auto-rebuild:
npm run watchFor detailed step-by-step instructions on how to deploy and test this MCP server, please see the
Quick setup:
- Build the server:
npm run build - Configure your Strapi instance and get an API token
- Add the server config to Claude Desktop:
On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"strapi-mcp": {
"command": "/path/to/strapi-mcp/build/index.js",
"env": {
"STRAPI_URL": "http://localhost:1337",
"STRAPI_API_TOKEN": "your-api-token-here",
"STRAPI_DEV_MODE": "false"
}
}
}
}STRAPI_URL(optional): The URL of your Strapi instance (defaults to http://localhost:1337)STRAPI_ADMIN_EMAIL&STRAPI_ADMIN_PASSWORD(Recommended): Credentials for a Strapi admin user. Required for full functionality like fetching content type schemas.STRAPI_API_TOKEN(Optional Fallback): Your Strapi API token. Can be used if admin credentials are not provided, but functionality might be limited based on token permissions.STRAPI_DEV_MODE(optional): Set to "true" to enable development mode features (defaults to false)
The server prioritizes authentication methods in this order:
- Admin Email & Password (
STRAPI_ADMIN_EMAIL,STRAPI_ADMIN_PASSWORD) - API Token (
STRAPI_API_TOKEN)
It's strongly recommended to use Admin Credentials for the best results.
- Admin Credentials: Use the email and password of an existing Super Admin or create a dedicated admin user in your Strapi admin panel (Settings > Administration Panel > Users).
- API Token: (Optional Fallback)
- Log in to your Strapi admin panel
- Go to Settings > API Tokens
- Click "Create new API Token"
- Set a name, description, and token type (preferably "Full access")
- Copy the generated token and use it in your MCP server configuration
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:
npm run inspectorThe Inspector will provide a URL to access debugging tools in your browser.
Once the MCP server is configured and running, you can use it with Claude to interact with your Strapi CMS. Here are some examples:
use_mcp_tool(
server_name: "strapi-mcp",
tool_name: "list_content_types",
arguments: {}
)
use_mcp_tool(
server_name: "strapi-mcp",
tool_name: "get_entries",
arguments: {
"contentType": "api::article.article",
"filters": {
"title": {
"$contains": "hello"
}
},
"pagination": {
"page": 1,
"pageSize": 10
},
"sort": ["title:asc"]
}
)
use_mcp_tool(
server_name: "strapi-mcp",
tool_name: "create_entry",
arguments: {
"contentType": "api::article.article",
"data": {
"title": "My New Article",
"content": "This is the content of my article.",
"publishedAt": "2023-01-01T00:00:00.000Z"
}
}
)
use_mcp_tool(
server_name: "strapi-mcp",
tool_name: "upload_media",
arguments: {
"fileData": "base64-encoded-data-here",
"fileName": "image.jpg",
"fileType": "image/jpeg"
}
)
use_mcp_tool(
server_name: "strapi-mcp",
tool_name: "connect_relation",
arguments: {
"contentType": "api::article.article",
"id": "1",
"relationField": "authors",
"relatedIds": [2, 3]
}
)
use_mcp_tool(
server_name: "strapi-mcp",
tool_name: "disconnect_relation",
arguments: {
"contentType": "api::article.article",
"id": "1",
"relationField": "authors",
"relatedIds": [3]
}
)
use_mcp_tool(
server_name: "strapi-mcp-local",
tool_name: "create_content_type",
arguments: {
"displayName": "My New Product",
"singularName": "product",
"pluralName": "products",
"kind": "collectionType",
"description": "Represents products in the store",
"draftAndPublish": true,
"attributes": {
"name": { "type": "string", "required": true },
"description": { "type": "text" },
"price": { "type": "decimal", "required": true },
"stock": { "type": "integer" }
}
}
)
use_mcp_tool(
server_name: "strapi-mcp-local",
tool_name: "update_content_type",
arguments: {
"contentType": "api::speaker.speaker",
"attributes": {
"isHighlightSpeaker": {
"type": "boolean",
"default": false
},
"newTextField": {
"type": "string"
}
}
}
)