Ghost MCP Server

Created By
MFYDeva year ago
A Model Context Protocol (MCP) server for interacting with Ghost CMS through LLM interfaces like Claude. Allow you to control your Ghost blog by simply asking Claude etc.
Overview

What is Ghost MCP Server?

Ghost MCP Server is a Model Context Protocol (MCP) server designed for seamless interaction with Ghost CMS through LLM interfaces like Claude. It allows users to manage their Ghost blog by simply asking Claude, providing a user-friendly way to control blog content and settings.

How to use Ghost MCP Server?

To use Ghost MCP Server, install it via Smithery or manually clone the repository. Set up the required environment variables for your Ghost Admin API, and configure it with your MCP client, such as Claude Desktop.

Key features of Ghost MCP Server?

  • Secure JWT Authentication for Ghost Admin API requests
  • Comprehensive access to blog entities including posts, users, members, tiers, offers, and newsletters
  • Advanced search functionality with fuzzy and exact matching options
  • Detailed output for Ghost entities
  • Robust error handling with custom exceptions
  • Integrated logging support for troubleshooting

Use cases of Ghost MCP Server?

  1. Managing blog posts and content through voice commands.
  2. Automating user and member management tasks.
  3. Creating and updating newsletters and promotional offers efficiently.

FAQ from Ghost MCP Server?

  • Can I use Ghost MCP Server with any version of Ghost?

It is recommended to use Ghost version 5.x or higher for optimal compatibility.

  • Is Ghost MCP Server secure?

Yes! It uses JWT authentication to ensure secure access to your Ghost Admin API.

  • How do I troubleshoot errors?

Ghost MCP Server provides clear error messages through custom GhostError exceptions to assist with troubleshooting.

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

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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