Ghost MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Ghost MCP Server?

Ghost MCP Server is a Model Context Protocol (MCP) server that integrates with the Ghost Admin API, allowing programmatic access to Ghost CMS features such as post, page, and member management.

how to use Ghost MCP Server?

To use the Ghost MCP Server, install it via npm, configure it with your Ghost Admin API key and URL, and start the server using the provided command.

key features of Ghost MCP Server?

  • Comprehensive post management (CRUD operations)
  • Page management capabilities
  • Member management with search functionality
  • Image upload support
  • Tag and author management

use cases of Ghost MCP Server?

  1. Automating blog post creation and management.
  2. Integrating Ghost CMS with other applications.
  3. Managing members and their subscriptions programmatically.

FAQ from Ghost MCP Server?

  • What are the prerequisites for using Ghost MCP Server?

You need Node.js (v18 or higher) and a Ghost CMS instance with an Admin API key.

  • Is there support for debugging?

Yes! You can use the MCP Inspector for debugging purposes.

  • What license is Ghost MCP Server under?

It is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
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