Strapi MCP Server
by MCP-Mirror
A Model Context Protocol server for interacting with Strapi CMS. This server enables AI assistants to interact with your Strapi instance through a standardized interface, supporting content types and REST API operations.
Last updated: N/A
What is Strapi MCP Server?
The Strapi MCP Server is a bridge that allows AI assistants to communicate with a Strapi CMS instance. It provides a standardized interface (Model Context Protocol) for interacting with Strapi's content types and REST API.
How to use Strapi MCP Server?
Install the server using npx and configure it with your Strapi API URL and JWT token. Use the provided JavaScript functions (e.g., strapi_list_servers, strapi_get_content_types, strapi_rest, strapi_upload_media) to interact with your Strapi instance. Refer to the documentation for specific usage examples and configuration options.
Key features of Strapi MCP Server
Schema introspection
REST API support with validation
Media upload handling
JWT authentication
Content type management
Image processing with format conversion
Multiple server support
Automatic schema validation
Write protection policy
Integrated documentation
Version compatibility management
Use cases of Strapi MCP Server
Enabling AI assistants to create, read, update, and delete content in Strapi
Automating content management tasks using AI
Building AI-powered applications that leverage Strapi as a backend
Integrating Strapi with other AI services and platforms
FAQ from Strapi MCP Server
How do I configure the server?
How do I configure the server?
Create a configuration file at ~/.mcp/strapi-mcp-server.config.json with your Strapi API URL, API key, and optional version.
How do I get a JWT token?
How do I get a JWT token?
Log in to your Strapi admin panel, create an API token with appropriate permissions, and add the token to your config file.
What versions of Strapi are supported?
What versions of Strapi are supported?
The server supports various version formats, including wildcard (e.g., "5._"), specific (e.g., "4.1.5"), and simple (e.g., "v4").
What is the write protection policy?
What is the write protection policy?
The server implements a strict write protection policy that requires explicit authorization for all write operations (POST, PUT, DELETE, Media Upload).
What are some best practices for using the server?
What are some best practices for using the server?
Always check schema first, use proper plural/singular forms for endpoints, include error handling, validate URLs before upload, start with minimal queries, always include the complete data object when updating, use filters to optimize query performance, leverage built-in schema validation, check version compatibility, and follow the write protection policy guidelines.