Skip to main content
Glama
robsoncoelho

Ghost + Contentful MCP

by robsoncoelho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Ghost + Contentful MCP

No user-submitted related servers found.

    Related Servers

    • ghost-mcp

      seagyn
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to manage Ghost CMS content through MCP, with read tools for posts, pages, tags, and members, plus draft-safe write tools that cannot publish or delete.
      4,678 npm
      MIT

    • Ghost MCP Server

      slb350
      A
      license
      Not graded
      quality
      D
      maintenance
      Manage your Ghost blog content directly from Claude, Cursor, or any MCP-compatible client, allowing you to create, edit, search, and delete posts with support for tag management and analytics.
      8 npm
      MIT

    • CrawlEyes

      waiky-github
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to perform web searches and extract full-text content from web pages via standard MCP tools, with fallback search and semantic reranking.
      2
      2
      MIT

    • ds-directory-mcp

      NoWorries
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables intent-based semantic search over external design system documentation, allowing MCP-compatible AI assistants to retrieve relevant design tokens, component architectures, and code patterns via a single tool.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    All tool names follow the exact same verb_noun pattern: 'search_' followed by a specific content type. This is perfectly consistent and predictable.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources