microCMS MCP サーバ

What is microCMS MCP サーバ?

It is an MCP (Model Context Protocol) server that provides access to the microCMS API, enabling AI assistants to retrieve, search, and filter content from microCMS. It is intended for developers using MCP-compatible clients (e.g., Claude Desktop) to interact with their microCMS headless CMS.

How to use microCMS MCP サーバ?

Clone the repository, install dependencies with npm install, build the TypeScript code with npm run build, then configure an MCP client (such as Claude Desktop) to run the built dist/index.js script. The required environment variables are MICROCMS_API_KEY (API key) and MICROCMS_BASE_URL (service endpoint). Tools are invoked by natural language prompts in the MCP client.

Key features of microCMS MCP サーバ

• Retrieve a list of contents from any endpoint
• Get a specific content by its ID
• Search contents by keyword
• Filter contents using complex conditions
• Expose content via URI resource templates

Use cases of microCMS MCP サーバ

• Fetch the latest blog posts from a microCMS endpoint
• Retrieve a specific article by ID
• Search for content matching a keyword
• Filter content by category or date range
• Integrate microCMS data into AI chat workflows

FAQ from microCMS MCP サーバ

What dependencies are required to run this server?

Node.js is required. The project uses TypeScript and must be compiled (npm run build) before use.

Where does the data live?

Data resides on the microCMS platform. The server only sends requests to the configured MICROCMS_BASE_URL and does not store any data locally.

What transport and authentication does it use?

It uses the MCP protocol (stdin/stdout). Authentication is via the MICROCMS_API_KEY environment variable sent with each request to microCMS.

Can it access draft (unpublished) content?

Yes. The get_content tool accepts an optional draftKey parameter to retrieve draft content.

How many items can be retrieved at once?

The limit parameter defaults to 10 and has a maximum of 100 for list, search, and filter tools.