microcms

This MCP server bridges microCMS with AI assistants by exposing the microCMS content management capabilities through the MCP protocol. It enables a variety of actions such as querying the latest articles, creating or editing content, reviewing and polishing content, and uploading media to microCMS. By using natural language prompts, an AI assistant can fetch, summarize, and annotate microCMS content, or perform publishing tasks within the microCMS space. The bundled tools cover content retrieval (e.g., listing or fetching items), content creation (drafting and submitting new entries), content review (checking for consistency, tone, or correctness), and media handling (uploading images or other assets).

Prerequisites:

• Node.js and npm (or npx available)
• A microCMS service with Service ID and API Key

Steps:

1. Install or run via npx using the provided MCP configuration. You can copy the snippet below into your MCP launcher or configuration file:

{
  "mcpServers": {
    "microcms": {
      "command": "npx",
      "args": ["-y", "microcms-mcp-server@latest"],
      "env": {
        "MICROCMS_SERVICE_ID": "<MICROCMS_SERVICE_ID>",
        "MICROCMS_API_KEY": "<MICROCMS_API_KEY>"
      }
    }
  }
}

2. Replace <MICROCMS_SERVICE_ID> and <MICROCMS_API_KEY> with your actual credentials.
3. Save the configuration and restart your MCP client or runtime environment to apply changes.
4. Verify that the MCP server is reachable by issuing a simple content query or a test prompt through your connected AI assistant.

If you prefer a local command-line run, ensure you have Node.js installed and run the same npx command manually in a terminal to verify connectivity before integrating into a larger setup.

Tips and notes:

• Keep your microCMS API credentials secure; consider using a secrets manager in production.
• After updating the configuration (e.g., changing service ID or API key), restart the client/app that loads the MCP server to ensure changes take effect.
• The MCP server supports content retrieval, creation, review, and media upload workflows. Craft prompts that align with these capabilities for best results.
• If you encounter authentication errors, double-check that the Service ID and API Key correspond to the same microCMS project and that the key has appropriate permissions.
• When using media uploads, ensure the target microCMS spaces have the necessary media fields or folders configured to receive assets.
• For debugging, log the MCP server output and enable verbose logs if the host allows it to diagnose payload or rate-limit issues.