LabscoMCP early access ↗
SpringMTMCP SERVER

microCMS Search MCP Server

Searches and reads microCMS content from the conversation — one endpoint, one API key.

by SpringMT ↗CMS & Blog PublishingCommunity

LABSCO 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: all three are required — the server exits at startup if any is missing. MICROCMS_ENDPOINT names the endpoint that search runs against. Build with npm run build, then point the client at the built build/index.js by absolute path.

Setup effort

Build from source — git clone https://github.com/SpringMT/microcms-mcp-server.git