Ghost MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GHOST_URL | Yes | The URL of your Ghost blog (e.g., https://your-blog.ghost.io) | |
| GHOST_ADMIN_API_KEY | No | Your Ghost Admin API key (id:secret format) for full CRUD access | |
| GHOST_CONTENT_API_KEY | Yes | Your Ghost Content API key for read-only access |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| content_browse_postsA | Browse published posts from Ghost Content API (read-only, public content). TIP: Use "fields" param (e.g., "id,title,slug,published_at,excerpt") to reduce response size. Omit html field unless content is needed. USE CASE:
NOTE: Only returns published posts visible to the public. For drafts, scheduled, or all posts, use admin_browse_posts instead. FILTER EXAMPLES:
RETURNS: Array of posts with pagination metadata (page, pages, total). |
| content_read_postA | Read a single published post by ID or slug (read-only, public content). USE CASE:
IDENTIFIER: Provide either 'id' OR 'slug', not both. NOTE: Only returns published posts visible to the public. For drafts or scheduled posts, use admin_read_post instead. RETURNS: Single post object with requested fields and related data (tags, authors). |
| content_browse_pagesA | Browse published pages from Ghost Content API (read-only, public content). TIP: Use "fields" param (e.g., "id,title,slug,published_at,excerpt") to reduce response size. Omit html field unless content is needed. USE CASE:
NOTE: Only returns published pages visible to the public. Pages are static content NOT shown in RSS feeds or blog listings. For drafts or all pages, use admin_browse_pages instead. RETURNS: Array of pages with pagination metadata (page, pages, total). |
| content_read_pageA | Read a single published page by ID or slug (read-only, public content). USE CASE:
IDENTIFIER: Provide either 'id' OR 'slug', not both. NOTE: Only returns published pages visible to the public. For drafts or scheduled pages, use admin_read_page instead. RETURNS: Single page object with requested fields and related data. |
| content_browse_tagsA | Browse public tags from Ghost Content API (read-only). USE CASE:
INCLUDE OPTIONS:
NOTE: Only returns public tags (not internal tags starting with #). For all tags including internal, use admin_browse_tags instead. RETURNS: Array of tags with metadata and optional post counts. |
| content_read_tagA | Read a single public tag by ID or slug (read-only). USE CASE:
IDENTIFIER: Provide either 'id' OR 'slug', not both. NOTE: Only returns public tags visible on the website. For internal tags, use admin_read_tag instead. RETURNS: Single tag object with metadata and optional post count. |
| content_browse_authorsA | Browse public authors from Ghost Content API (read-only). USE CASE:
INCLUDE OPTIONS:
NOTE: Only authors with at least one published post are returned. For all staff users (including those without posts), use admin_browse_users instead. RETURNS: Array of authors with bio, social links, and optional post counts. |
| content_read_authorA | Read a single public author by ID or slug (read-only). USE CASE:
IDENTIFIER: Provide either 'id' OR 'slug', not both. NOTE: Only returns authors with published posts. For staff users without published posts, use admin_read_user instead. RETURNS: Single author object with bio, social links, and optional post count. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/workspace/ghost-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server