Strapi MCP Server
remote-capable server
The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.
Integrations
Integrates with Strapi CMS to provide access to content types and entries through the MCP protocol, allowing creation, reading, updating, and deletion of content entries, as well as media uploads
strapi-mcp MCP Server
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
Features
Resources
- 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
Tools
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 Strapi
Advanced Features
Filtering, Pagination, and Sorting
The get_entries
tool supports advanced query options:
Resource URIs
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
Development
Install dependencies:
Build the server:
For development with auto-rebuild:
Installation
For detailed step-by-step instructions on how to deploy and test this MCP server, please see the DEPLOYMENT.md file.
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
Environment Variables
STRAPI_URL
(optional): The URL of your Strapi instance (defaults to http://localhost:1337)STRAPI_API_TOKEN
(required): Your Strapi API token for authenticationSTRAPI_DEV_MODE
(optional): Set to "true" to enable development mode features (defaults to false)
Getting a Strapi API Token
- 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
Debugging
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:
The Inspector will provide a URL to access debugging tools in your browser.
Usage Examples
Once the MCP server is configured and running, you can use it with Claude to interact with your Strapi CMS. Here are some examples:
Listing Content Types
Getting Entries
Creating an Entry
Uploading Media
Accessing Resources
This server cannot be installed
Provides access to Strapi CMS content through the MCP protocol, allowing users to create, read, update, and delete content entries via Claude.