microcms-document

This MCP server provides access to microCMS documentation for use by AI assistants. It exposes tools that let you fetch general microCMS information, list available documentation files in the docs directory, and read the content of a specific documentation file. After setup, you can prompt the AI to query microCMS docs and it will read the relevant documents on demand to craft informed responses. Use the explicit trigger like use microcms-docs-mcp in your chat to request MCP features.

Available tools:

• fetch_general: Returns general information about microCMS.
• list_documents: Lists the filenames of documentation documents available under the docs directory.
• search_document: Retrieves the content of a specified documentation file. Use this to read the details inside a particular document. These tools enable targeted access to up-to-date documentation and enable the AI to base answers on the latest microCMS docs as needed.

Prerequisites:

• Node.js (recommended) and npm/yarn installed on your system.
• Basic familiarity with MCP clients and integrating an MCP server into your workflow.

Step 1: Install Node.js and npm in your environment if not already installed.

• Visit https://nodejs.org/ and follow the installation instructions for your OS.

Step 2: Start the MCP server using npx (no global installation required).

• Run the following command to run the server directly via npx:

npx -y microcms-document-mcp-server

Step 3 (optional): Persist installation in your project by listing it in your package.json.

• You can install locally as a dev dependency:

npm install --save-dev microcms-document-mcp-server

• Then start the server with a script defined in package.json, e.g.:

"scripts": {
  "start-mcp": "node node_modules/microcms-document-mcp-server/dist/index.js"
}

Step 4: Configure the MCP client to use this server (example provided in the README).

• For MCP clients, configure the server under the mcpServers block as shown in the mcp_config example.

Tips and considerations:

• The MCP server relies on the microCMS documentation files being available under the docs directory. Ensure the docs directory exists and contains your documentation files.
• If you customize the server name, update the mcp_config accordingly in your MCP client configuration.
• No API keys are included in this MCP server by default; if your workflow requires authenticated access to microCMS, consider environment variables or integration steps on the client side to supply keys securely.
• When using npx, you’re running a temporary installation of the package; for persistent usage, consider installing the package locally in your project.
• If you encounter permission or network issues with npx, ensure your npm configuration allows package fetches and that your network can reach the npm registry.
• The available tools are intentionally scoped to fetch_general, list_documents, and search_document. Extend or customize the docs directory to expand the toolset.