Skip to main content
Glama
intellieffect

Agentic CMS

by intellieffect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Agentic CMS

No user-submitted related servers found.

    Related Servers

    • @writavo/mcp-server

      SparkleOfficial
      A
      license
      A
      quality
      B
      maintenance
      MCP server that connects AI assistants to Writavo CMS, enabling content creation, publishing, scheduling, and media management through natural language, with safety confirmations for irreversible actions.
      38
      755 npm
      MIT

    • mcp-content-ops

      nitti510x
      A
      license
      B
      quality
      B
      maintenance
      An MCP server that enables agents to safely interact with CMS content, with deny-by-default write policies, type/field allowlists, and structured audit trails.
      5
      MIT
    • ledric by getledric

      ledricofficial

      getledric
      A
      license
      Not graded
      quality
      C
      maintenance
      A self-hosted content engine with an MCP interface that enables AI agents to read, write, and manage content models through tools like describe_model, create_type, draft, and publish.
      Apache 2.0

    • TypeScript WordPress MCP

      bokazio
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for WordPress content management that provides a secure interface for AI assistants to interact with WordPress sites, enabling content creation, editing, and media management without destructive operations.
      MIT
    • Cosmic MCP Server by cosmicjs

      Cosmic MCP Serverofficial

      cosmicjs
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that enables AI assistants to manage content, media, and schemas within Cosmic CMS buckets. It allows users to perform CRUD operations on objects and types while providing tools for AI-driven text, image, and video generation.
      19
      60 npm
      1
      MIT
    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

    B3.3/5.0

    Scored across 52 tools

    Disambiguation4/5

    Most tools target a distinct resource+action, and pipeline-step labels in descriptions aid selection. However, the 'media' family (list_media, list_gallery_media, list_videos) and gallery cover tools (set_gallery_cover vs attach_gallery_media role=cover) have overlapping boundaries that require careful reading.

    Naming Consistency5/5

    Every tool uses snake_case with a consistent verb_noun pattern (list_*, get_*, create_*, update_*, delete_*, send_*). A few longer names like create_blog_post_from_markdown and link_video_project_to_variant remain readable and follow the same convention.

    Tool Count2/5

    52 tools is well beyond the 25-tool threshold for a heavy server and risks overwhelming an agent's selection space. Although the server spans many subdomains (blog, gallery, video, carousel, social publishing, pipeline), the surface is bloated and could be split or consolidated.

    Completeness4/5

    Core pipeline and CRUD flows are well covered: ideas (list/get/create/update/promote), gallery items (full CRUD), carousels, contents, variants, and publishing. Minor gaps exist, notably missing delete/update operations for blog posts, carousels, contents, variants, media, and video projects, though agents can generally work around these.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources