Ghost Publisher runs on your own machine — the client starts it, so there is no endpoint to ping. 102 installs a week from npm. Last commit 25 Aug 2026.
Local-first MCP server for safe Ghost authoring, diagnostics, scheduling, and publishing.
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 26 August 2026. No other catalogue keeps this.
We read the source, 4 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
пакет ghost-publisher-mcp ссылается на blogfactoryhq/ghost-publisher-mcp
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add ghost-publisher -e 'GHOST_URL=<GHOST_URL>' -e 'GHOST_ADMIN_API_KEY=<GHOST_ADMIN_API_KEY>' -- npx -y ghost-publisher-mcp
{
"mcpServers": {
"ghost-publisher": {
"command": "npx",
"args": [
"-y",
"ghost-publisher-mcp"
],
"env": {
"GHOST_ADMIN_API_KEY": "<GHOST_ADMIN_API_KEY>",
"GHOST_URL": "<GHOST_URL>"
}
}
}
}
[mcp_servers.ghost-publisher]
command = "npx"
args = ["-y", "ghost-publisher-mcp"]
env = { GHOST_URL = "<GHOST_URL>", GHOST_ADMIN_API_KEY = "<GHOST_ADMIN_API_KEY>" }
{
"mcpServers": {
"ghost-publisher": {
"command": "npx",
"args": [
"-y",
"ghost-publisher-mcp"
],
"env": {
"GHOST_ADMIN_API_KEY": "<GHOST_ADMIN_API_KEY>",
"GHOST_URL": "<GHOST_URL>"
}
}
}
}
{
"servers": {
"ghost-publisher": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"ghost-publisher-mcp"
],
"env": {
"GHOST_ADMIN_API_KEY": "<GHOST_ADMIN_API_KEY>",
"GHOST_URL": "<GHOST_URL>"
}
}
}
}
Put your own values in place of
<GHOST_URL> (URL of the Ghost site), <GHOST_ADMIN_API_KEY> (Admin API key from a Ghost custom integration).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
GHOST_API_VERSION (Ghost Admin API compatibility version; defaults to v5.0), GHOST_PERMISSION_PROFILE (Permission profile: read-only, draft-editor, scheduler, or publisher. Defaults to publisher), GHOST_READ_ONLY (Legacy alias for the read-only profile. Do not combine with GHOST_PERMISSION_PROFILE), GHOST_UPLOAD_ROOTS (Allowed absolute directories for local image uploads), GHOST_DEPLOY_HOOK_URL (Optional deployment hook called once after a completely successful publish or unpublish batch), GHOST_PUBLIC_POST_URL_TEMPLATE (Optional public post URL containing {slug} for live checks), GHOST_PUBLIC_PAGE_URL_TEMPLATE (Optional public page URL containing {slug} for headless live checks).
Local-first MCP server for safe Ghost authoring, diagnostics, scheduling, and publishing.
A hosted MCP server for planning, scheduling, media, analytics, and social publishing.
Official TimeToPost MCP server for social post drafting, scheduling, publishing and approval queues.
One MCP server for mod platforms and local modding diagnostics. No data kept.
Local MCP server for AI-assisted Apache Tomcat management and diagnostics
PostKing MCP server for managing brands, generating posts, scheduling content, and publishing blogs.
Local-first social MCP: an agent drafts and schedules posts; you approve before anything publishes.
Local-first MCP server and CLI for validating and generating synthetic ACH files.
Answers built from our own checks of this server.