What can you do with this server?

This server lets AI assistants interact with microCMS via MCP: manage content, media, schemas, members, and multiple services. * Content operations: list/search/get/create (published/draft), bulk create, update, patch, and delete contents on any endpoint. * Metadata/status control: retrieve meta information, change publish/draft status, set or clear publish/stop reservations, and change the content creator. * Media management: list, upload (via base64 or external URL), and delete media files. * Schema discovery: get available endpoints, API schemas, and configured services, including serviceId discovery for multi-service mode. * Member management: fetch member details. * Multi-service support: select a service per tool with serviceId, or use single-service mode with default credentials. * Flexible deployment: run as a local stdio server or as a remote HTTP server with bearer auth.

Which integrations are available for this server?

Enables configuration of microCMS credentials through environment variables loaded from a .env file. Provides code linting capabilities for the project, available through npm scripts. Serves as the runtime environment for the MCP server, with a minimum requirement of Node.js 18.0.0 or higher. Used for package management and running scripts to build, start, and develop the MCP server. Offers code formatting functionality for the project, available through npm scripts. Used as the development language for the MCP server, with build scripts to compile TypeScript to JavaScript.

How do I use microCMS MCP Server?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@microCMS MCP Server get the latest 5 blog posts from microCMS" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

microCMS MCP Server

by microcmsio

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

microCMS MCP Server (Local)

WARNING

このローカルMCPサーバーは、原則として今後更新されません。

新規利用には、microCMSがホストするリモートMCPサーバーの利用を推奨します。

microCMS のローカル環境で動作するMCP（Model Context Protocol）サーバーです。 ClaudeなどのAIアシスタントがmicroCMSのコンテンツ管理システムとやり取りできるようにします。

必要なもの

microCMSのサービスIDとAPIキー

Related MCP server: Kintone MCP Server

セットアップ

方法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_SERVICE_ID>",
        "MICROCMS_API_KEY": "<MICROCMS_API_KEY>"
      }
    }
  }
}

<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_SERVICE_ID` + `MICROCMS_API_KEY`	単一サービス	省略可（自動でデフォルトサービスを使用）
`MICROCMS_SERVICES` (JSON)	複数サービス	必須

従来の環境変数設定をそのまま使う場合、serviceIdを指定せずに今まで通り動作します
両方の設定が存在する場合、MICROCMS_SERVICES が優先されます

利用方法

microCMSのコンテンツを確認する

microCMSの news から最新の記事を10件取得してください

microCMSにコンテンツを作成して入稿する

MCPサーバーの概要や利用例について調べ、それを1000文字程度でまとめてmicroCMSの blogs に入稿してください

microCMSのコンテンツを取得してレビューしてもらう

microCMSの xxxxxx のコンテンツを取得して、日本語的におかしい部分があれば指摘して

microCMSのメディア一覧に画像をアップロードする

次の画像をmicroCMSにアップロードして。

- https://example.com/sample-image-1.png
- https://example.com/sample-image-2.png
- https://example.com/sample-image-3.png

複数サービスモードでの使用例

複数サービスモードでは、サービスIDを指定して各サービスを操作できます。

blogサービスの記事一覧を取得して

shopサービスに新しい商品を追加して

blogの最新記事をshopの商品説明にコピーして

サービス一覧の確認

microcms://services リソースを読み取ることで、設定済みサービスと各サービスのAPI（エンドポイント）一覧を確認できます。AIエージェントはこの情報を使って、指定されたendpointがどのサービスに属するか判断できます。

{
  "mode": "multi",
  "description": "Multi service mode - serviceId parameter is required for all tools. Use the serviceId that contains the endpoint you need.",
  "services": [
    {
      "id": "blog",
      "apis": [
        { "name": "ブログ記事", "endpoint": "blogs", "type": "list" },
        { "name": "カテゴリー", "endpoint": "categories", "type": "list" }
      ]
    },
    {
      "id": "shop",
      "apis": [
        { "name": "商品", "endpoint": "products", "type": "list" },
        { "name": "注文", "endpoint": "orders", "type": "list" }
      ]
    }
  ]
}

方法4: リモートMCPサーバー（HTTP）として使う

HTTPトランスポートを使って、リモートMCPサーバーとして起動できます。チームメンバーや外部ツールから共有利用する場合に便利です。

HTTPモードでは MCP_AUTH_TOKEN が必須です。未設定・空文字・空白のみの場合は起動に失敗します。stdioモードでは不要です。以前のバージョンで認証なしのHTTP接続を利用していた場合は、更新前にサーバーのトークンとクライアントの Authorization: Bearer <token> ヘッダーを設定してください。

サーバー側の起動

# 単一サービス
MICROCMS_SERVICE_ID=my-blog \
MICROCMS_API_KEY=your-api-key \
MCP_TRANSPORT=http \
MCP_AUTH_TOKEN=my-shared-secret \
npx microcms-mcp-server

# 複数サービス
MICROCMS_SERVICES='[{"id":"blog","apiKey":"key1"},{"id":"shop","apiKey":"key2"}]' \
MCP_TRANSPORT=http \
MCP_AUTH_TOKEN=my-shared-secret \
npx microcms-mcp-server

クライアント側の設定（mcp-remote経由）

{
  "mcpServers": {
    "microcms-remote": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "http://your-server:3000/mcp",
        "--header", "Authorization:Bearer my-shared-secret"
      ]
    }
  }
}

Dockerで起動

# ビルド
npm run build
docker build -t microcms-mcp .

# 起動
MCP_AUTH_TOKEN=my-secret \
MICROCMS_SERVICES='[{"id":"blog","apiKey":"key1"}]' \
docker compose up -d

📖 Docker を使ったセットアップ、クライアント別の接続設定、トラブルシューティングの詳細は DOCKER.md を参照してください。

CLIオプション

オプション	環境変数	デフォルト	説明
`--transport`	`MCP_TRANSPORT`	`stdio`	トランスポートモード（`stdio` または `http`）
`--port`	`MCP_HTTP_PORT`	`3000`	HTTPサーバーのポート番号
`--host`	`MCP_HTTP_HOST`	`0.0.0.0`	HTTPサーバーのホスト
-	`MCP_AUTH_TOKEN`	-	Bearer認証トークン（HTTPでは必須、stdioでは不要）

より詳しい使い方

以下の記事でより詳しい使い方を紹介しています。

ライセンス

MIT

Available Tools

22 tools

microcms_create_content_draftC

Create new content in microCMS and publish it immediately.

Important

Ensure that the "content" you submit strictly adheres to the following specifications. In particular, take extra care when handling custom fields and iframe fields, as mistakes are common in their structure. Read the instructions thoroughly and construct the data precisely as described. In particular, for extended fields (iframe fields), you need to take care to call microcms_get_list tool beforehand, and set its structure to the "data" field (Detail is described below).

Field type specifications

Image fields require URL string uploaded to microCMS media library (e.g., "https://images.microcms-assets.io/assets/xxx/yyy/sample.png").
Multiple image fields use array format.
Rich editor fields expect HTML strings.
Date fields use ISO 8601 format.
Select fields use arrays.
Content reference fields use contentId strings or arrays for multiple references, and you can get contentIds from microcms_get_list tool.
Custom field exepect below struct:

<field Id in apiFields> {
  "fieldId": "<target custom field id in customFields>"
  "key1": "<value1>",
  "key2": "<value2>",
}

iframe field (Extension field) expects the following structure for CREATE/UPDATE:

  {
    "id": "some-id",
    "title": "some-title",
    "description": "some-description",
    "imageUrl": "https://images.microcms-assets.io/assets/xxxx/yyyy/{fileName}.png",
    "updatedAt": "2024-01-01T00:00:00Z",
    "data": { "key1": "value1", "key2": "value2" }
  }

IMPORTANT: When retrieving content via API, only the "data" object content is returned (without the wrapper).
IMPORTANT: When creating/updating content, you MUST provide the full structure including id, title, description, imageUrl, updatedAt, and data.
To understand the "data" structure, ALWAYS use microcms_get_list to retrieve existing content first and examine the field structure.
"id", "title", "description", "imageUrl" are metadata displayed in the admin screen and are not included in the API GET response.

Inputs: content (required), endpoint (required), contentId, serviceId.

microcms_create_content_publishedA

Create new content in microCMS and publish it immediately.

Important

Field type specifications

Image fields require URL string uploaded to microCMS media library (e.g., "https://images.microcms-assets.io/assets/xxx/yyy/sample.png").
Multiple image fields use array format.
Rich editor fields expect HTML strings.
Date fields use ISO 8601 format.
Select fields use arrays.
Content reference fields use contentId strings or arrays for multiple references, and you can get contentIds from microcms_get_list tool.
Custom field exepect below struct:

<field Id in apiFields> {
  "fieldId": "<target custom field id in customFields>"
  "key1": "<value1>",
  "key2": "<value2>",
}

iframe field (Extension field) expects the following structure for CREATE/UPDATE:

  {
    "id": "some-id",
    "title": "some-title",
    "description": "some-description",
    "imageUrl": "https://images.microcms-assets.io/assets/xxxx/yyyy/{fileName}.png",
    "updatedAt": "2024-01-01T00:00:00Z",
    "data": { "key1": "value1", "key2": "value2" }
  }

IMPORTANT: When retrieving content via API, only the "data" object content is returned (without the wrapper).
IMPORTANT: When creating/updating content, you MUST provide the full structure including id, title, description, imageUrl, updatedAt, and data.
To understand the "data" structure, ALWAYS use microcms_get_list to retrieve existing content first and examine the field structure.
"id", "title", "description", "imageUrl" are metadata displayed in the admin screen and are not included in the API GET response.

Inputs: content (required), endpoint (required), contentId, serviceId.

microcms_create_contents_bulk_draftB

Create multiple contents in microCMS at once. This tool processes contents sequentially and continues even if some fail. Results include success/failure status for each content.

Create new content in microCMS and publish it immediately.

Important

Field type specifications

Image fields require URL string uploaded to microCMS media library (e.g., "https://images.microcms-assets.io/assets/xxx/yyy/sample.png").
Multiple image fields use array format.
Rich editor fields expect HTML strings.
Date fields use ISO 8601 format.
Select fields use arrays.
Content reference fields use contentId strings or arrays for multiple references, and you can get contentIds from microcms_get_list tool.
Custom field exepect below struct:

<field Id in apiFields> {
  "fieldId": "<target custom field id in customFields>"
  "key1": "<value1>",
  "key2": "<value2>",
}

iframe field (Extension field) expects the following structure for CREATE/UPDATE:

  {
    "id": "some-id",
    "title": "some-title",
    "description": "some-description",
    "imageUrl": "https://images.microcms-assets.io/assets/xxxx/yyyy/{fileName}.png",
    "updatedAt": "2024-01-01T00:00:00Z",
    "data": { "key1": "value1", "key2": "value2" }
  }

IMPORTANT: When retrieving content via API, only the "data" object content is returned (without the wrapper).
IMPORTANT: When creating/updating content, you MUST provide the full structure including id, title, description, imageUrl, updatedAt, and data.
To understand the "data" structure, ALWAYS use microcms_get_list to retrieve existing content first and examine the field structure.
"id", "title", "description", "imageUrl" are metadata displayed in the admin screen and are not included in the API GET response.

Inputs: contents (required), endpoint (required), serviceId.

microcms_create_contents_bulk_publishedA

Create multiple contents in microCMS at once. This tool processes contents sequentially and continues even if some fail. Results include success/failure status for each content.

Create new content in microCMS and publish it immediately.

Important

Field type specifications

Image fields require URL string uploaded to microCMS media library (e.g., "https://images.microcms-assets.io/assets/xxx/yyy/sample.png").
Multiple image fields use array format.
Rich editor fields expect HTML strings.
Date fields use ISO 8601 format.
Select fields use arrays.
Content reference fields use contentId strings or arrays for multiple references, and you can get contentIds from microcms_get_list tool.
Custom field exepect below struct:

<field Id in apiFields> {
  "fieldId": "<target custom field id in customFields>"
  "key1": "<value1>",
  "key2": "<value2>",
}

iframe field (Extension field) expects the following structure for CREATE/UPDATE:

  {
    "id": "some-id",
    "title": "some-title",
    "description": "some-description",
    "imageUrl": "https://images.microcms-assets.io/assets/xxxx/yyyy/{fileName}.png",
    "updatedAt": "2024-01-01T00:00:00Z",
    "data": { "key1": "value1", "key2": "value2" }
  }

IMPORTANT: When retrieving content via API, only the "data" object content is returned (without the wrapper).
IMPORTANT: When creating/updating content, you MUST provide the full structure including id, title, description, imageUrl, updatedAt, and data.
To understand the "data" structure, ALWAYS use microcms_get_list to retrieve existing content first and examine the field structure.
"id", "title", "description", "imageUrl" are metadata displayed in the admin screen and are not included in the API GET response.

Inputs: contents (required), endpoint (required), serviceId.

microcms_delete_contentC

Delete content from microCMS

Inputs: endpoint (required), contentId (required), serviceId.

microcms_delete_mediaA

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.

Inputs: url (required), serviceId.

microcms_get_api_infoC

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.

Inputs: endpoint (required), serviceId.

microcms_get_api_listB

Get list of all available APIs (endpoints) from microCMS Management API. Returns API name, endpoint, and type (list/object) for each API.

Inputs: serviceId.

microcms_get_contentC

Get a specific content from microCMS

Inputs: endpoint (required), contentId (required), depth, fields, +2 more.

microcms_get_content_metaA

Get a specific content with metadata from microCMS Management API. IMPORTANT: Use this tool ONLY when the user message contains "メタ" (meta) or "メタ情報" (metadata). This API returns metadata information such as status, createdBy, updatedBy, reservationTime, closedAt, and customStatus that are not available in the regular content API. For regular content retrieval, use microcms_get_content instead.

Inputs: endpoint (required), contentId (required), serviceId.

microcms_get_listB

Get a list of contents from microCMS

Inputs: endpoint (required), q, ids, depth, +7 more.

microcms_get_list_metaA

Get a list of contents with metadata from microCMS Management API. IMPORTANT: Use this tool ONLY when the user message contains "メタ" (meta) or "メタ情報" (metadata). This API returns metadata information such as status, createdBy, updatedBy, reservationTime, closedAt, and customStatus that are not available in the regular content API. For regular content retrieval, use microcms_get_list instead.

Inputs: endpoint (required), limit, offset, serviceId.

microcms_get_mediaA

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.

Inputs: limit, token, fileName, imageOnly, +1 more.

microcms_get_memberA

Get a specific member from microCMS Management API. Returns member information including ID, name, email, and MFA status.

Inputs: memberId (required), serviceId.

microcms_get_servicesA

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.

Inputs: no named parameters.

microcms_patch_contentD

Create new content in microCMS and publish it immediately.

Important

Field type specifications

Image fields require URL string uploaded to microCMS media library (e.g., "https://images.microcms-assets.io/assets/xxx/yyy/sample.png").
Multiple image fields use array format.
Rich editor fields expect HTML strings.
Date fields use ISO 8601 format.
Select fields use arrays.
Content reference fields use contentId strings or arrays for multiple references, and you can get contentIds from microcms_get_list tool.
Custom field exepect below struct:

<field Id in apiFields> {
  "fieldId": "<target custom field id in customFields>"
  "key1": "<value1>",
  "key2": "<value2>",
}

iframe field (Extension field) expects the following structure for CREATE/UPDATE:

  {
    "id": "some-id",
    "title": "some-title",
    "description": "some-description",
    "imageUrl": "https://images.microcms-assets.io/assets/xxxx/yyyy/{fileName}.png",
    "updatedAt": "2024-01-01T00:00:00Z",
    "data": { "key1": "value1", "key2": "value2" }
  }

IMPORTANT: When retrieving content via API, only the "data" object content is returned (without the wrapper).
IMPORTANT: When creating/updating content, you MUST provide the full structure including id, title, description, imageUrl, updatedAt, and data.
To understand the "data" structure, ALWAYS use microcms_get_list to retrieve existing content first and examine the field structure.
"id", "title", "description", "imageUrl" are metadata displayed in the admin screen and are not included in the API GET response.

Inputs: content (required), endpoint (required), contentId (required), isDraft, +1 more.

microcms_patch_content_created_byB

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.

Inputs: endpoint (required), contentId (required), createdBy (required), serviceId.

microcms_patch_content_statusB

Change content publication status in microCMS (Management API). Can change status between PUBLISH (published) and DRAFT (draft). Note: Only transitions between "published" and "draft" are supported.

Inputs: status (required), endpoint (required), contentId (required), serviceId.

microcms_update_content_draftD

Create new content in microCMS and publish it immediately.

Important

Field type specifications

Image fields require URL string uploaded to microCMS media library (e.g., "https://images.microcms-assets.io/assets/xxx/yyy/sample.png").
Multiple image fields use array format.
Rich editor fields expect HTML strings.
Date fields use ISO 8601 format.
Select fields use arrays.
Content reference fields use contentId strings or arrays for multiple references, and you can get contentIds from microcms_get_list tool.
Custom field exepect below struct:

<field Id in apiFields> {
  "fieldId": "<target custom field id in customFields>"
  "key1": "<value1>",
  "key2": "<value2>",
}

iframe field (Extension field) expects the following structure for CREATE/UPDATE:

  {
    "id": "some-id",
    "title": "some-title",
    "description": "some-description",
    "imageUrl": "https://images.microcms-assets.io/assets/xxxx/yyyy/{fileName}.png",
    "updatedAt": "2024-01-01T00:00:00Z",
    "data": { "key1": "value1", "key2": "value2" }
  }

IMPORTANT: When retrieving content via API, only the "data" object content is returned (without the wrapper).
IMPORTANT: When creating/updating content, you MUST provide the full structure including id, title, description, imageUrl, updatedAt, and data.
To understand the "data" structure, ALWAYS use microcms_get_list to retrieve existing content first and examine the field structure.
"id", "title", "description", "imageUrl" are metadata displayed in the admin screen and are not included in the API GET response.

Inputs: content (required), endpoint (required), contentId (required), serviceId.

microcms_update_content_publishedD

Create new content in microCMS and publish it immediately.

Important

Field type specifications

Image fields require URL string uploaded to microCMS media library (e.g., "https://images.microcms-assets.io/assets/xxx/yyy/sample.png").
Multiple image fields use array format.
Rich editor fields expect HTML strings.
Date fields use ISO 8601 format.
Select fields use arrays.
Content reference fields use contentId strings or arrays for multiple references, and you can get contentIds from microcms_get_list tool.
Custom field exepect below struct:

<field Id in apiFields> {
  "fieldId": "<target custom field id in customFields>"
  "key1": "<value1>",
  "key2": "<value2>",
}

iframe field (Extension field) expects the following structure for CREATE/UPDATE:

  {
    "id": "some-id",
    "title": "some-title",
    "description": "some-description",
    "imageUrl": "https://images.microcms-assets.io/assets/xxxx/yyyy/{fileName}.png",
    "updatedAt": "2024-01-01T00:00:00Z",
    "data": { "key1": "value1", "key2": "value2" }
  }

IMPORTANT: When retrieving content via API, only the "data" object content is returned (without the wrapper).
IMPORTANT: When creating/updating content, you MUST provide the full structure including id, title, description, imageUrl, updatedAt, and data.
To understand the "data" structure, ALWAYS use microcms_get_list to retrieve existing content first and examine the field structure.
"id", "title", "description", "imageUrl" are metadata displayed in the admin screen and are not included in the API GET response.

Inputs: content (required), endpoint (required), contentId (required), serviceId.

microcms_update_content_reservationA

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.

Inputs: endpoint (required), contentId (required), stopTime, serviceId, +1 more.

microcms_upload_mediaA

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.

Inputs: fileData, fileName, mimeType, serviceId, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.6/5.0

Scored 2026-06-26 20:30 across 22 tools

Disambiguation2/5

Multiple tools (microcms_create_content_published, microcms_patch_content, microcms_update_content_draft) have identical descriptions that claim to create new content and publish immediately, making it impossible to distinguish their actual purpose. The overlap between create, patch, and update variants is severe.

Naming Consistency3/5

All tools use the microcms_ prefix and snake_case, following a verb_noun pattern. However, there are inconsistencies like microcms_create_contents_bulk vs microcms_create_content (plural vs singular), and the verbs 'patch' vs 'update' are used without clear distinction.

Tool Count3/5

22 tools is on the high side for a CMS MCP server, but the scope covers content, media, members, services, and APIs. Some consolidation could reduce redundancy, but the count is still reasonable.

Completeness3/5

The tool set covers most CRUD operations for content and media, plus metadata, member info, and service discovery. Missing are bulk update/delete and member management (create/update/delete). The duplicate create/patch tools obscure actual functionality.

Maintenance

ActivitySlowing

ResponsivenessNo recent community issues

Resources

Related MCP Connectors

hithereiamaliff-mcp-nextcloud
ai.smithery
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Cloud Storage File Systems Workplace & Productivity
239
https://server.smithery.ai/@hithereiamaliff/mcp-nextcloud/mcp
mcpC
com.wix
A Model Context Protocol server for Wix AI tools
Developer Tools Content Management Systems App Automation
215
https://mcp.wix.com/mcp
Airtable MCP by InsightfulPipeA
com.insightfulpipe
Hosted Airtable MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Databases Workplace & Productivity
41
https://airtable.insightfulmcp.com/
Notion MCP by InsightfulPipeA
com.insightfulpipe
Hosted Notion MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Note Taking Workplace & Productivity
41
https://notion.insightfulmcp.com/

Related MCP Servers

Strapi MCP Server
Content Management Systems Developer Tools
misterboe
A
license
A
quality
B
maintenance
A Model Context Protocol server that enables AI assistants to interact with Strapi CMS instances through a standardized interface, supporting content types and REST API operations.
Updated 2 months ago (2026-09-11 12:25 UTC)
5
93 npm
75
MIT
Kintone MCP Server
Cloud Platforms Developer Tools
r3-yamauchi
A
license
C
quality
D
maintenance
A Model Context Protocol server that enables Claude and other AI assistants to access and update Kintone data through natural language commands, supporting operations like record management, file handling, app administration, and space collaboration.
Updated 20 days ago (2026-10-23 21:36 UTC)
79
10
AGPL 3.0
microCMS MCP Server
Search Content Management Systems
SpringMT
A
license
B
quality
D
maintenance
A Model Context Protocol (MCP) compliant server that allows Large Language Models (LLMs) to search and retrieve content from microCMS APIs.
Updated 2 years ago (2025-03-19 01:52 UTC)
2
MIT
Contentful MCP Server
Content Management Systems Developer Tools App Automation
tejedamiguel6
A
license
C
quality
Not graded
maintenance
A Model Context Protocol server that enables Claude to interact directly with Contentful CMS, allowing the AI to fetch content types and entries from a Contentful space.
Updated 2 years ago (2025-05-08 01:26 UTC)
2
2
MIT

Appeared in Searches

Shopify: E-commerce Platform for Online Stores

microCMS MCP Server (Local)

必要なもの

セットアップ

方法1: MCP Bundle (旧DXTファイル) を使う

方法2: npx をつかう（単一サービス）

方法3: 複数サービスを使う

複数サービスモードの動作

後方互換性

利用方法

複数サービスモードでの使用例

サービス一覧の確認

方法4: リモートMCPサーバー（HTTP）として使う

サーバー側の起動

クライアント側の設定（mcp-remote経由）

Dockerで起動

CLIオプション

より詳しい使い方

ライセンス

Available Tools

Important

Field type specifications

Important

Field type specifications

Important

Field type specifications

Important

Field type specifications

Important

Field type specifications

Important

Field type specifications

Important

Field type specifications

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Strapi MCP Server

Kintone MCP Server

microCMS MCP Server

Contentful MCP Server

Appeared in Searches