Skip to main content
Glama
SpringMT

microCMS MCP Server

by SpringMT
README.md
# microCMS MCP Server

Model Context Protocol (MCP) 対応の microCMS 検索サーバーです。LLM から microCMS のコンテンツを検索・取得するために使用できます。

## 機能

- microCMS APIを使用したコンテンツの検索
- 特定のコンテンツの取得
- MCP (Model Context Protocol) 準拠のインターフェース


## 必要な環境変数の説明

- `MICROCMS_API_KEY`: microCMSのAPIキー(必須)
- `MICROCMS_SERVICE_DOMAIN`: microCMSのサービスドメイン(必須)
- `MICROCMS_ENDPOINT`: 利用するエンドポイント

## ビルド

```bash
npm run build
```

## 使い方

### MCPクライアントからの使用

このサーバーはMCPプロトコルに準拠しているため、MCP対応のLLMクライアントから呼び出すことができます。

```
{
    "mcpServers": {
        "microcms": {
            "command": "node",
            "args": [
                "/ABSOLUTE/PATH/TO/PARENT/FOLDER/build/index.js"
            ],
            "env": {
                "MICROCMS_API_KEY": "",
                "MICROCMS_SERVICE_DOMAIN": "",
                "MICROCMS_ENDPOINT": ""
            }
        }
    }
}
```



## 関連リンク

- [microCMS](https://microcms.io/)
- [Model Context Protocol](https://modelcontextprotocol.ai/)
- [microcms-js-sdk](https://github.com/microcmsio/microcms-js-sdk) 

TDQS

B3/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: GetMicroCMSContent retrieves a specific item by ID, while SearchMicroCMS performs a broader query across content. There is no overlap in functionality, making it easy for an agent to choose the right tool for the task.

Naming Consistency5/5

Both tools follow a consistent naming pattern with a verb (Get or Search) followed by the domain (MicroCMS) and a noun (Content). They use consistent PascalCase styling, making the naming predictable and readable.

Tool Count2/5

With only two tools, the server feels under-scoped for a content management system. It lacks essential CRUD operations like create, update, or delete, which are typically expected for managing content. The count is too low for the apparent domain.

Completeness2/5

The toolset is severely incomplete for a CMS server. It only provides read operations (get and search), missing create, update, delete, and other lifecycle management functions. This will cause agent failures when full content management is required.

Maintenance

ActivityInactive
ResponsivenessNo issues