strapi cms.com
strapi cms.com logo

Strapi CMS

Integrates Strapi CMS content into workflows, enabling manipulation of data for content management and querying in Strap...

Created byApr 22, 2025

Strapi MCP Server

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.
IMPORTANT DISCLAIMER: This software has been developed with the assistance of AI technology. It is provided as-is and should NOT be used in production environments without thorough testing and validation. The code may contain errors, security vulnerabilities, or unexpected behavior. Use at your own risk for research, learning, or development purposes only.

Changelog

Version 2.3.0 - Documentation & Configuration Enhancement

  • Added comprehensive project documentation in CLAUDE.md
  • Expanded configuration options with better version detection
  • Enhanced troubleshooting guides for common issues
  • Detailed REST API documentation with practical examples
  • Best practices guide for content management
  • Fixed version parsing from different format patterns
  • Improved error messaging with version-specific guidance

Version 2.2.0 - Security & Version Handling Update

  • Added strict write protection policy
  • Enhanced version format support (5.* , 4.1.5, v4, etc.)
  • Integrated documentation into server capabilities
  • Removed connect prompt (now in capabilities)
  • Improved error handling and validation
  • Added version-specific differences guide
  • Enhanced server capabilities documentation

Version 2.1.0

  • Improved compatibility with both Strapi v4 and v5
  • Removed automatic validation to support different data structures between versions
  • Enhanced error messages with version-specific hints
  • Simplified request handling to give clients more control
  • Updated documentation with clear examples for both versions

Features

  • 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

Installation

You can use this server directly with npx in your Claude Desktop configuration:

Configuration

Create a configuration file at ~/.mcp/strapi-mcp-server.config.json:
You can configure multiple Strapi instances by adding them to this file.

Version Configuration

The server now supports various version formats:
  • Wildcard: "5.", "4."
  • Specific: "4.1.5", "5.0.0"
  • Simple: "v4", "v5"
This helps the server provide version-specific guidance and handle API differences appropriately.

Getting a JWT Token

  1. Log in to your Strapi admin panel
  1. Create an API token with appropriate permissions
  1. Add the token to your config file under the appropriate server name

Usage

List Available Servers

Content Types

REST API

The REST API provides comprehensive CRUD operations with built-in validation and version-specific handling:

Media Upload

Version Differences (v4 vs v5)

Key differences between Strapi versions that the server handles automatically:

v4

  • Uses numeric IDs
  • Nested attribute structure
  • Data wrapper in responses
  • Traditional REST patterns
  • External i18n plugin

v5

  • Document-based IDs
  • Flat data structure
  • Direct attribute access
  • Enhanced JWT security
  • Integrated i18n support
  • New Document Service API

Security Features

Write Protection Policy

The server implements a strict write protection policy:
  • All write operations require explicit authorization
  • Protected operations include:
  • Each operation is logged and validated

Best Practices

  1. Always check schema first with strapi_get_content_types
  1. Use proper plural/singular forms for endpoints
  1. Include error handling in your queries
  1. Validate URLs before upload
  1. Start with minimal queries and add population only when needed
  1. Always include the complete data object when updating
  1. Use filters to optimize query performance
  1. Leverage built-in schema validation
  1. Check version compatibility for your operations
  1. Follow the write protection policy guidelines

REST API Tips

Filtering

Sorting

Pagination

Population

Troubleshooting

Common issues and solutions:
  1. 404 Errors
  1. Authentication Issues
  1. Version-Related Issues
  1. Write Protection Errors

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

MIT

Strapi MCP Server

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.
IMPORTANT DISCLAIMER: This software has been developed with the assistance of AI technology. It is provided as-is and should NOT be used in production environments without thorough testing and validation. The code may contain errors, security vulnerabilities, or unexpected behavior. Use at your own risk for research, learning, or development purposes only.

Changelog

Version 2.3.0 - Documentation & Configuration Enhancement

  • Added comprehensive project documentation in CLAUDE.md
  • Expanded configuration options with better version detection
  • Enhanced troubleshooting guides for common issues
  • Detailed REST API documentation with practical examples
  • Best practices guide for content management
  • Fixed version parsing from different format patterns
  • Improved error messaging with version-specific guidance

Version 2.2.0 - Security & Version Handling Update

  • Added strict write protection policy
  • Enhanced version format support (5.* , 4.1.5, v4, etc.)
  • Integrated documentation into server capabilities
  • Removed connect prompt (now in capabilities)
  • Improved error handling and validation
  • Added version-specific differences guide
  • Enhanced server capabilities documentation

Version 2.1.0

  • Improved compatibility with both Strapi v4 and v5
  • Removed automatic validation to support different data structures between versions
  • Enhanced error messages with version-specific hints
  • Simplified request handling to give clients more control
  • Updated documentation with clear examples for both versions

Features

  • 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

Installation

You can use this server directly with npx in your Claude Desktop configuration:

Configuration

Create a configuration file at ~/.mcp/strapi-mcp-server.config.json:
You can configure multiple Strapi instances by adding them to this file.

Version Configuration

The server now supports various version formats:
  • Wildcard: "5.", "4."
  • Specific: "4.1.5", "5.0.0"
  • Simple: "v4", "v5"
This helps the server provide version-specific guidance and handle API differences appropriately.

Getting a JWT Token

  1. Log in to your Strapi admin panel
  1. Create an API token with appropriate permissions
  1. Add the token to your config file under the appropriate server name

Usage

List Available Servers

Content Types

REST API

The REST API provides comprehensive CRUD operations with built-in validation and version-specific handling:

Media Upload

Version Differences (v4 vs v5)

Key differences between Strapi versions that the server handles automatically:

v4

  • Uses numeric IDs
  • Nested attribute structure
  • Data wrapper in responses
  • Traditional REST patterns
  • External i18n plugin

v5

  • Document-based IDs
  • Flat data structure
  • Direct attribute access
  • Enhanced JWT security
  • Integrated i18n support
  • New Document Service API

Security Features

Write Protection Policy

The server implements a strict write protection policy:
  • All write operations require explicit authorization
  • Protected operations include:
  • Each operation is logged and validated

Best Practices

  1. Always check schema first with strapi_get_content_types
  1. Use proper plural/singular forms for endpoints
  1. Include error handling in your queries
  1. Validate URLs before upload
  1. Start with minimal queries and add population only when needed
  1. Always include the complete data object when updating
  1. Use filters to optimize query performance
  1. Leverage built-in schema validation
  1. Check version compatibility for your operations
  1. Follow the write protection policy guidelines

REST API Tips

Filtering

Sorting

Pagination

Population

Troubleshooting

Common issues and solutions:
  1. 404 Errors
  1. Authentication Issues
  1. Version-Related Issues
  1. Write Protection Errors

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

MIT