microCMSSAFE
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[!WARNING] このローカルMCPサーバーは、原則として今後更新されません。 新規利用には、microCMSがホストするリモートMCPサーバーの利用を推奨します。
microCMS のローカル環境で動作するMCP(Model Context Protocol)サーバーです。 ClaudeなどのAIアシスタントがmicroCMSのコンテンツ管理システムとやり取りできるようにします。
必要なもの
- microCMSのサービスIDとAPIキー
セットアップ
方法1: MCP Bundle (旧DXTファイル) を使う
Claude Desktopに導入する場合、mcpbファイルを使って簡単にインストールできます。
- リリースページ から最新の
microcms-mcp-server.mcpbをダウンロード - ダウンロードしたmcpbファイルをダブルクリックで開く
- サービスIDとAPIキーを設定する
方法2: npx をつかう(単一サービス)
{
"mcpServers": {
"microcms": {
"command": "npx",
"args": ["-y", "microcms-mcp-server@latest"],
"env": {
"MICROCMS_SERVICE_ID": "",
"MICROCMS_API_KEY": ""
}
}
}
}`, ` はご自身のものに置き換えてください。
設定更新後はクライアントを再起動してください。
方法3: 複数サービスを使う
複数のmicroCMSサービスに接続する場合は、MICROCMS_SERVICES 環境変数にJSON形式でサービス情報を設定します。
{
"mcpServers": {
"microcms-multi": {
"command": "npx",
"args": ["-y", "microcms-mcp-server@latest"],
"env": {
"MICROCMS_SERVICES": "[{\"id\":\"blog\",\"apiKey\":\"xxx-api-key\"},{\"id\":\"shop\",\"apiKey\":\"yyy-api-key\"}]"
}
}
}
}複数サービスモードの動作
複数サービスモードでは、各ツールに serviceId パラメータが必須になります。
- ツール名は単一サービスモードと同じ
microcms_*形式です - 各ツール呼び出し時に
serviceIdを指定してサービスを選択します - 設定済みサービスの一覧は
microcms_get_servicesツールで確認できます - MCPリソース
microcms://servicesからも同様の情報を取得できます
後方互換性
- 従来の環境変数設定をそのまま使う場合、serviceIdを指定せずに今まで通り動作します
- 両方の設定が存在する場合、
MICROCMS_SERVICESが優先されます
利用方法
microCMSのコンテンツを確認する
microCMSの news から最新の記事を10件取得してください
m
2236cee29e03OBSERVED · 2026-10-10Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add microcms-mcp-server --env MCP_AUTH_TOKEN=${MCP_AUTH_TOKEN} --env MICROCMS_API_KEY=${MICROCMS_API_KEY} -- npx -y [email protected]{
"mcpServers": {
"microcms-mcp-server": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"MCP_AUTH_TOKEN": "${MCP_AUTH_TOKEN}",
"MICROCMS_API_KEY": "${MICROCMS_API_KEY}"
}
}
}
}Exposed tools (15)
9 read · 3 write · 3 destructive. Blast radius: 3 tools can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.
| Tool | Risk | Description |
|---|---|---|
microcms_delete_content | destructive | Delete content from microCMS |
microcms_delete_media | destructive | Delete media files from microCMS (Management API). Supports deletion of both images and files. Requires media deletion permissions. Note: Media referenced by content cannot be deleted. |
microcms_get_api_info | read | Get API schema information from microCMS Management API. In relation and relationList field, you can get its schema using referencedApiEndpoint and microcms_get_api_info tool. |
microcms_get_api_list | read | Get list of all available APIs (endpoints) from microCMS Management API. Returns API name, endpoint, and type (list/object) for each API. |
microcms_get_content | read | Get a specific content from microCMS |
microcms_get_content_meta | read | Get a specific content with metadata from microCMS Management API. IMPORTANT: Use this tool ONLY when the user message contains |
microcms_get_list | read | Get a list of contents from microCMS |
microcms_get_list_meta | read | Get a list of contents with metadata from microCMS Management API. IMPORTANT: Use this tool ONLY when the user message contains |
microcms_get_media | read | Get media files from microCMS (Management API). Returns media information including URLs, dimensions for images. Supports pagination via token (15-second validity). Requires media retrieval permissions. |
microcms_get_member | read | Get a specific member from microCMS Management API. Returns member information including ID, name, email, and MFA status. |
microcms_get_services | read | Get list of configured microCMS services and their available APIs (endpoints). Use this tool first to discover which services are available and find the correct serviceId for other tools. In multi-service mode, serviceId is required for all other tools. |
microcms_patch_content_created_by | write | Change content creator in microCMS (Management API). Updates the createdBy field of a content item to a specified member ID. Member ID can be found in the member detail screen in the management console. |
microcms_patch_content_status | write | Change content publication status in microCMS (Management API). Can change status between PUBLISH (published) and DRAFT (draft). Note: Only transitions between |
microcms_update_content_reservation | destructive | Set or clear content publish/stop reservation schedules in microCMS (Management API). Provide publishTime and/or stopTime as ISO 8601 strings. If neither is provided, existing publish and stop reservations are cleared. |
microcms_upload_media | write | Upload media files to microCMS using JS SDK (Management API). Supports two methods: 1) Upload file data (base64) with filename and mimeType, 2) Upload from external URL. Returns microCMS asset URL. Requires media upload permissions. Available on Team, Business, Advanced, and Enterprise plans. |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (2 observation(s))
- Network
- declared (7 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (2)
microcms_delete_content, microcms_delete_media, microcms_update_content_reservation
@hono/mcp, @hono/node-server, @modelcontextprotocol/sdk, hono, microcms-js-sdk, @types/node, typescript
Gates applied: no_behavioural_pass.
2236cee29e03full audit observations/trust-audit/mcp-server/microcmsio__microcms-2.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-10 | 2236cee29e03 | SAFE | B | 89 | first audit |
Questions
What tools does microCMS expose?
15 in total: 9 read-only, 3 that write, and 3 that can delete or overwrite (microcms_delete_content, microcms_delete_media, microcms_update_content_reservation). Every one is listed on this page with its risk.
Is microCMS safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B. Separately from the audit: 3 of its tools can destroy data, so scope the token you give it to what you actually need.
What credentials does microCMS need?
It reads MCP_AUTH_TOKEN and MICROCMS_API_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does microCMS run?
It speaks stdio and streamable-http, so it runs as a local process your client starts. It is published on npm as microcms-mcp-server at 0.12.0.
How current is this page?
The grade is for one exact copy of the source (2236cee29e03), read on 2026-10-10. The repository is watched and re-audited when it changes.