strapi

This MCP server provides a standardized interface to interact with a Strapi CMS instance. It exposes REST-like operations for content types, components, and media, with built-in validation, schema introspection, and optional JWT-based authentication. You can query content types, fetch components with pagination, perform CRUD operations via the REST API wrapper, and upload media with automatic processing. The server is designed to help AI assistants generate, validate, and manipulate Strapi data through a consistent, version-aware surface that adapts to v4 or v5 Strapi deployments.

To use it, configure a Strapi instance URL and a JWT token in the provided config file, then expose operations through the MCP interface. The tooling includes content type discovery, REST-style CRUD operations (GET, POST, PUT, DELETE) with validation, media upload handling, and version-aware guidance to accommodate differences between Strapi v4 and v5. The server also exposes helpers for listing servers, fetching content types, and performing filtered queries, making it straightforward to build AI-driven workflows that read or modify Strapi content while respecting write-protection policies.

Prerequisites:

• Node.js (LTS version) installed on your machine
• npm or pnpm
• Access to run npx (no global install required)

1. Ensure Node.js and npm are installed:

node -v
npm -v

2. Install and run the MCP server via npx (as documented in the README):

# Using the MCP server via npx (no local install needed)
npx -y @bschauer/strapi-mcp-server@2.6.0

3. Create the MCP configuration file for Strapi:

// ~/.mcp/strapi-mcp-server.config.json
{
  "myserver": {
    "api_url": "http://localhost:1337",
    "api_key": "your-jwt-token-from-strapi-admin",
    "version": "5.*" // or another version pattern
  }
}

4. If you prefer a local install approach, you can place the MCP server config in your project and run it through npx as shown above. The configuration file supports multiple Strapi instances by adding additional entries under the "myserver" key with their respective api_url and api_key.

Tips and considerations:

• The server supports both Strapi v4 and v5; ensure your version string matches your deployment for correct API handling.
• Store JWT tokens securely and avoid embedding them in public repos. Use environment-specific config files when possible.
• If you encounter 404 or authentication issues, verify the API URL, token validity, and that the correct server name is used in your queries.
• The configuration supports multiple Strapi instances; you can manage different environments (dev, staging, prod) by adding more entries.
• Review the REST API tips and filtering options in the README to construct efficient queries and population payloads.
• When dealing with media uploads, ensure your Strapi instance has the necessary permissions and that you provide valid media URLs and target fields.