ghost-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GHOST_API_URL | Yes | The URL of your Ghost site, e.g. https://yoursite.ghost.io | |
| GHOST_API_VERSION | Yes | The Ghost API version, must be a v5.x value (e.g. v5.0). Other versions may cause 404 errors. | |
| GHOST_ADMIN_API_KEY | Yes | Your Ghost Admin API key in the format <id>:<secret> |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize-post |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| blog-info |
TDQS
Scored across 36 tools
Resource prefixes (tiers, offers, posts, etc.) are distinct, but the absence of descriptions makes browse vs read and draft vs non-draft actions ambiguous. Members vs users also have unclear boundaries, and overlapping action names across resources compound the issue.
All tools follow a consistent snake_case pattern of [plural_resource]_[action] (e.g., tiers_read, posts_add). The draft subresource pattern (posts_draft_add) is also applied uniformly, and action verbs (browse, read, add, edit) are reused predictably.
At 36 tools, the set is heavy for the apparent scope, even though it covers nine resources. Many tools are repetitive action variants that could be consolidated, and the lack of descriptions makes the large surface harder to navigate.
Core CRUD is incomplete: no delete operations exist for any resource, and posts/pages have draft creation/editing but no publish, unpublish, or schedule actions. Media handling, settings, and other common CMS lifecycle operations are also absent, causing significant gaps for agent workflows.