Ghost + Contentful MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GHOST_API_KEY | Yes | The Ghost content API key | |
| CONTENTFUL_SPACE_ID | Yes | The Contentful space ID | |
| GHOST_CONTENT_ENDPOINT | Yes | The Ghost content API endpoint URL | |
| CONTENTFUL_ACCESS_TOKEN | Yes | The Contentful access token |
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 |
|---|---|
| search_blog_postsA | Search Ghost CMS blog posts by matching query against title, excerpt, and body content. Returns all matching posts. |
| search_blog_pagesA | Search Ghost CMS pages by matching query against title and body content. Returns all matching pages. |
| search_learn_pagesA | Search Contentful learn pages by matching query against title, meta title, meta description, and body content. Returns all matching pages. |
| search_case_studiesA | Search Contentful case studies (success stories) by matching query against company name, meta title, meta description, overview, quote, use case, impact, and body content. Returns all matching case studies. |
| search_eventsA | Search Contentful events (internal event pages and event cards) by matching query against title, description, and body content. Returns all matching events. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct content type (learn pages, case studies, events, blog posts, blog pages), and the descriptions clearly specify the fields searched. There is no ambiguity between Contentful and Ghost entities.
All tool names follow the exact same verb_noun pattern: 'search_' followed by a specific content type. This is perfectly consistent and predictable.
The server has 5 tools, well within the ideal 3-15 range. Each tool covers a distinct searchable content type, so every tool earns its place without redundancy or bloat.
The tool surface is entirely search-focused, covering the apparent primary content types across both CMSs. Minor gaps exist, such as no ability to fetch a single content item by ID or search across all content types at once, but these are not critical for a search-oriented server.