Misterboe Strapi MCP Server

🚀 Strapi MCP Server

The Strapi MCP (Model Context Protocol) Server allows AI assistants to interact with Strapi instances through a standardized interface, supporting content types and REST API operations.

🚀 Quick Start

📦 Installation

Run the following command directly using npx in the Claude Desktop configuration to install the server:

npx strapi-mcp-server

Create a Configuration File

Create or edit the configuration file ~/.mcp/strapi-mcp-server.config.json and add the following content:

{
  "apiUrl": "http://localhost:1337", // URL of the Strapi instance, default is http://localhost:1337
  "version": "v5",                 // Supported Strapi version, optional values: v4, v5
  "jwtToken": "your_jwt_token"     // JWT authentication token for Strapi
}

✨ Features

Core Features

1. Content Query:

   • Retrieve single or multiple content entries.
   • Support filtering, sorting, and pagination.

2. Media Upload:

   • Upload images or other files.
   • Automatically perform format conversion and optimization (e.g., WebP).
   • Support custom metadata.

3. Version Support:

   • Support different API structures and data formats of Strapi v4 and v5.

Usage Examples

Query Content

// Get a single article
strapi_get_content({
  server: "default",
  endpoint: "articles",
  id: "123"
});

// Get multiple articles and paginate
strapi_get_content({
  server: "default",
  endpoint: "articles",
  params: {
    pagination: { page: 1, pageSize: 25 },
    sort: ["createdAt:desc"]
  }
});

Media Upload

// Upload and optimize an image
strapi_upload_media({
  server: "default",
  url: "https://example.com/image.jpg",
  format: "webp",
  quality: 80,
  metadata: {
    name: "My Image",
    caption: "Image Caption",
    alternativeText: "Alt Text"
  }
});

🔧 Technical Details

Version Differences (v4 vs v5)

v4

• Use numeric IDs.
• Nested attribute structure.
• Response data is wrapped in a data wrapper.
• Traditional REST pattern.
• External i18n plugin.

v5

• Use document IDs.
• Flattened data structure.
• Direct access to attributes.
• Enhanced JWT security.
• Integrated i18n support.
• New document service API.

Security Features

Write Protection Policy

The server enforces strict write protection:

• All write operations (POST, PUT, DELETE) require explicit authorization.
• Protected operations include:
  • Creation (POST)
  • Update (PUT)
  • Deletion (DELETE)
  • Media upload
• Each operation is logged and verified.

💡 Usage Tip

Best Practices

1. Check Content Types: Use strapi_get_content_types to confirm fields and structures.
2. Use URL Formats Correctly: Distinguish between plural and singular endpoints.
3. Include Error Handling: Add exception catching to each request.
4. Set Appropriate Permissions: Control API access based on roles and permissions.

Troubleshooting

Common Issues

1. 401 Unauthorized Error:

   • Check if the JWT token is correctly configured.
   • Ensure the token is enabled in the Strapi instance.

2. 404 Resource Not Found:

   • Verify that the endpoint name and ID are correct.
   • Confirm that the API endpoints of the Strapi instance are correctly set.

3. Data Format Error:

   • Check if the request parameters match the target version (v4 or v5).
   • Ensure that the passed data structure meets the requirements.

🤝 Contribution Guidelines

Community contributions are welcome! Please improve the project by submitting Pull Requests.

• Submit issues: GitHub Issues
• Submit features or fixes: Pull Request

With the above documentation, developers can quickly get started and efficiently use the Strapi MCP Server for content management and media processing.