Summary
Scoped by the endpoint you name.
The configuration is the access-control story: the key, the service domain and the endpoint together decide what the model can see, so a narrow endpoint keeps the rest of the CMS out of reach. It reads content — there is no publishing path here.
What it is
An MCP server for microCMS. It lets a model search content in a microCMS service and fetch a specific entry, so a draft can be written against what is actually published rather than a copy of it.
What you get
- Content search across a microCMS endpoint, run through the microCMS API
- A specific piece of content fetched by itself, once the search has found it
- A published-content view of your CMS, scoped to the service domain and endpoint you configure
- Built on the official `microcms-js-sdk`
Requirements
A microCMS account with an API key. Three environment variables carry the configuration: `MICROCMS_API_KEY` and `MICROCMS_SERVICE_DOMAIN` are required, and `MICROCMS_ENDPOINT` names the endpoint to use. Build with `npm run build`, then point the client at the built `build/index.js` by absolute path.