Summary

Draft, publish and schedule microCMS content without opening the dashboard.

The draft and scheduling tools are what make this usable for real editorial work rather than demos: an item can be created as a draft, previewed through a draftKey, then moved to PUBLISH or given a publish and stop time. Reading the endpoint's schema first means generated content matches the field definitions instead of guessing at them. One thing to weigh before building on it: microCMS points new setups at its own hosted remote server and does not plan further updates to this local package.

What it is

MicroCMS's local server across both its Content API and its Management API: list and fetch content, create it published or as a draft, update or patch it, move its publication status, schedule publish and stop times, and manage media and API schemas — for one service or several at once.

What you get

Content listed with the full query surface — q, filters, fields, orders, limit, offset, ids, depth, and a draftKey for previewing unpublished items
One content item fetched by ID, with or without its metadata
Content created published or as a draft, one at a time or in bulk — the bulk call carries on past individual failures and reports each result
Content replaced or patched, and its status moved between PUBLISH and DRAFT
Publish and stop times scheduled as ISO 8601 strings, or cleared again
The createdBy field reassigned to another member
Content deleted
Media listed with pagination, uploaded from base64 data or an external URL, and deleted
API schemas read — every endpoint with its name and type, and one endpoint's field definitions, including following a relation field to the schema it points at
Several microCMS services behind one server, chosen per call with serviceId and listed through a tool or the microcms://services resource

Requirements

A microCMS service ID and API key. For a single service, MICROCMS_SERVICE_ID and MICROCMS_API_KEY; for several, MICROCMS_SERVICES as a JSON array of id and apiKey pairs, which makes serviceId required on every call and wins if both are set. Launch with npx microcms-mcp-server@latest over stdio, install the .mcpb bundle in Claude Desktop, or run it as a shared HTTP server with MCP_TRANSPORT=http on MCP_HTTP_PORT 3000 behind an MCP_AUTH_TOKEN bearer, for which a Docker setup is provided.

Setup effort

One command plus a key — npx microcms-mcp-server, then supply credentials