Strapi

You can connect Strapi CMS instances to your AI-powered assistant with this MCP server. It provides a standardized interface to interact with Strapi content types and REST API operations, enabling safe, validated interactions and version-aware behavior.

How to use

You interact with Strapi through the MCP server by configuring a connection, then issuing operations via your MCP client. You can list available Strapi servers, inspect content types and components, query and modify content using REST-like operations, and upload media with optional image processing. The server handles validation, version differences between Strapi v4 and v5, and writes-protection rules to keep your data safe.

Practical patterns you can apply include listing content types to learn what you can read or modify, querying articles with filters and sorts, creating new entries, updating existing ones, and deleting content when permitted. You can also upload images with automatic format conversion. Use the content-type aware REST-like operations to ensure you work with the correct fields and nested structures for your Strapi instance.

How to install

Prerequisites: ensure Node.js and npm are installed on your system. Check versions with node -v and npm -v.

1. Install or run the MCP server client via npx using the example configuration shown here.

{
  "mcpServers": {
    "strapi": {
      "command": "npx",
      "args": ["-y", "@bschauer/strapi-mcp-server@2.6.0"]
    }
  }
}

2. Create a local MCP configuration for your Strapi instance. This file stores the API URL, API token, and optional version details.

{
  "myserver": {
    "api_url": "http://localhost:1337",
    "api_key": "your-jwt-token-from-strapi-admin",
    "version": "5.*" 
  }
}

3. Save the file at the path ~/.mcp/strapi-mcp-server.config.json. You can configure multiple Strapi instances by adding more server entries to this file.

Configuration

Create a configuration file at the path ~/.mcp/strapi-mcp-server.config.json with your Strapi API URL, API token, and optional version spec. The server supports per-server configuration so you can manage several Strapi instances from a single MCP client.

Example configuration snippet is shown in the installation steps above. Use the same structure, replacing values with your actual Strapi endpoint and credentials.

Security and best practices

The server validates inputs and enforces a write-protection policy. Write operations (Create, Update, Delete, and Media Upload) require explicit authorization. Each operation is logged for traceability. Check that your API token is valid and has the necessary permissions, and verify version compatibility when performing operations that differ between Strapi v4 and v5.

REST API tips

Use filters to narrow queries, apply sorting on fields like createdAt, and leverage pagination to control result sets. When updating, provide the full data object to avoid missing fields and adhere to the version-specific data structure of your Strapi instance.

Example capabilities you can exercise include listing content types, retrieving content with filters, creating and updating entries, deleting entries with proper authorization, and uploading media with optional image optimization.

Troubleshooting

If you encounter issues, verify the following: the Strapi endpoint is reachable, the provided API token is valid and has required permissions, and the requested operation aligns with the Strapi version in use. For write-related problems, ensure the operation is permitted by the write-protection policy.

Available tools

strapi_list_servers

List available Strapi MCP servers along with version information and differences between Strapi v4 and v5.

strapi_get_content_types

Retrieve all content types from a specified Strapi server.

strapi_get_components

Fetch components with pagination for a given server.

strapi_rest

Perform REST API operations (GET, POST, PUT, DELETE) against Strapi endpoints with built-in validation and version-specific handling.

strapi_upload_media

Upload and process media assets to Strapi, with optional format conversion and metadata.