By using microCMS MCP, you can retrieve and manipulate microCMS content and service information using natural language from AI that supports the Model Context Protocol (MCP).
Since microCMS hosts the MCP server, users do not need to start an MCP server in their local environment. You can use it by setting the service connection URL and API Key in the MCP client.

Available Tools

This section lists the tools available in microCMS MCP (units of provided functions and operations) along with the corresponding APIs for each tool.
The available tools are subject to the permissions of the configured API Key. To use tools that perform write operations, an API Key with the necessary permissions for the target operations is required.

Settings

Authentication Method

microCMS MCP uses HTTP Bearer authentication with an API Key. OAuth authentication is not supported at this time.

microCMS Configuration

Obtain the Service ID and API Key for the service you will use with microCMS MCP.
Please grant the necessary permissions to the API Key to execute the APIs corresponding to the tools you wish to use. For detailed configuration instructions, please refer to "API Key (API Authentication and Permission Management)".

MCP Client-Side Settings

Here, we will introduce some examples of settings for various clients.

ChatGPT App

1. Open the settings in the ChatGPT app.
2. Open the plugins and select the MCP tab.
3. Select [Add MCP Server] from the Add menu.
4. Choose [Streamable HTTP] as the connection method.
5. Enter the following and save. Replace ${MICROCMS_SERVICE_ID} and ${MICROCMS_API_KEY} with your own Service ID and API Key.

Codex

Add the following to ~/.codex/config.toml. Replace ${MICROCMS_SERVICE_ID} and ${MICROCMS_API_KEY} with your own Service ID and API Key.

[mcp_servers.microcms]
url = "https://mcp.microcms.io/mcp/${MICROCMS_SERVICE_ID}"
http_headers = { Authorization = "Bearer ${MICROCMS_API_KEY}" }

Claude Code

Run the following command. Replace ${MICROCMS_SERVICE_ID} and ${MICROCMS_API_KEY} with your own Service ID and API Key.

claude mcp add --transport http microcms \
  https://mcp.microcms.io/mcp/${MICROCMS_SERVICE_ID} \
  --header "Authorization: Bearer ${MICROCMS_API_KEY}"

Cursor

Add the following to ~/.cursor/mcp.json. Replace ${MICROCMS_SERVICE_ID} and ${MICROCMS_API_KEY} with your own Service ID and API Key.

{
  "mcpServers": {
    "microcms": {
      "url": "https://mcp.microcms.io/mcp/${MICROCMS_SERVICE_ID}",
      "headers": {
        "Authorization": "Bearer ${MICROCMS_API_KEY}"
      }
    }
  }
}

Notion Custom Agent

1. Open the target custom agent.
2. Go to Tools and Access in the settings.
3. Select [Add Connection] and then [Add Custom MCP].
4. Enter the following and click [Connect]. Replace ${MICROCMS_SERVICE_ID} and ${MICROCMS_API_KEY} with your own Service ID and API Key.

Permission Settings for Safe Use

In microCMS MCP, to prevent unintended operations, it is recommended to limit the allowed actions to the bare minimum through two layers: the permissions of the API Key on the microCMS side and the tools enabled on the MCP client side.

1. Restrict API Key Permissions

When using microCMS MCP, it is recommended to create a dedicated API Key for AI operations, separate from the API Key used in production environments.
The actions that can be executed in microCMS MCP are governed by the permissions of the configured API Key. Please grant only the necessary permissions for the intended use to the AI operation-specific API Key.

2. Limit Tools Used in the MCP Client

If the MCP client allows enabling or disabling tools individually, please restrict the tools available to AI to only those that are necessary.
For example, if only content retrieval is to be performed, use an API Key with permissions only for retrieval, and disable tools related to creation, updating, and deletion on the MCP client side.

By restricting the actions that can be executed in microCMS MCP with the API Key and limiting the tools available to AI on the MCP client side, you can use microCMS MCP with the minimum necessary permissions.

Notes

• Uploading media may take time or may not complete successfully depending on how the MCP client processes file data.
• API requests via microCMS MCP are sent from the MCP server hosted by microCMS. Since the source IP address is not fixed, it may not be usable for services that have API IP Restriction set.
• When manipulating content via microCMS MCP, it is treated as an operation through the API.
• For information on the MCP server used in a local environment, please refer to the GitHub repository.