microCMS MCP Server

Created By
SpringMTa year ago
Overview

What is microCMS MCP Server?

The microCMS MCP Server is a search server that allows you to search and retrieve content from microCMS using the Model Context Protocol (MCP). It is designed to work with large language models (LLMs) to access microCMS content efficiently.

How to use microCMS MCP Server?

To use the microCMS MCP Server, you need to set up the required environment variables, build the project, and then call it from an MCP-compliant client. The server can be invoked using a command that specifies the path to the built index file and the necessary environment variables.

Key features of microCMS MCP Server?

  • Search for content using the microCMS API.
  • Retrieve specific content based on queries.
  • Compliant with the Model Context Protocol (MCP) interface.

Use cases of microCMS MCP Server?

  1. Integrating microCMS content retrieval into AI applications.
  2. Building chatbots that can fetch and display content from microCMS.
  3. Enhancing LLMs with dynamic content from microCMS.

FAQ from microCMS MCP Server?

  • What is required to run the microCMS MCP Server?

You need to set the MICROCMS_API_KEY, MICROCMS_SERVICE_DOMAIN, and MICROCMS_ENDPOINT environment variables.

  • Can I use this server with any LLM?

Yes! As long as the LLM client supports the MCP protocol, it can interact with the microCMS MCP Server.

  • Is there a specific programming language required?

The server is built using TypeScript, but it can be called from any language that can execute commands.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
SpringMT
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago