Skip to main content
Glama
hybriden

Paperboy CMS

Official
by hybriden
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Paperboy CMS

  • agent-cms

    jokull
    A
    license
    Not graded
    quality
    A
    maintenance
    Agent-first headless CMS running as a Cloudflare Worker, providing MCP servers for schema/content management and editorial operations.
    10 npm
    4
    MIT

Related Servers

  • 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

  • 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

  • NavoCMS

    Tsumibito
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to draft, review, preview, and publish content across multiple websites through typed MCP tools. Ensures safe, policy-gated, and auditable publication without requiring a conventional CMS admin interface.
    Apache 2.0

  • Inhalt

    kozmos-tech
    A
    license
    Not graded
    quality
    D
    maintenance
    An MCP-native CMS that lets you create and edit content by chatting, with typed schemas and seamless publishing.
    4 npm
    3
    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

A4.1/5.0

Scored across 64 tools

Disambiguation4/5

Most tools target distinct resources and actions, and the descriptions sharply separate draft editing, delivery reads, tree browsing, types/templates, assets, forms, redirects, users, and webhooks. Some overlap remains—especially list_content/list_tree/delivery_list/delivery_search and update_content/set_field—but the guidance is usually sufficient to choose correctly.

Naming Consistency4/5

The set predominantly follows a snake_case verb_noun convention (list_content, create_redirect, delete_asset, update_user). Minor deviations like publish/unpublish and the delivery_* prefix are readable and intentional, though they break strict uniformity.

Tool Count1/5

64 tools is far beyond a typical agent-manageable surface and creates substantial selection overhead. Even though the CMS domain is broad, this many granular admin operations is an extreme count rather than a well-scoped set.

Completeness5/5

The surface covers content CRUD, publishing, versions, trash, trees, content types/templates, assets, stock images, forms/submissions, delivery API, redirects/404s, users, keys, webhooks, audit, locales, and AI assistance. No obvious lifecycle or operational gap stands out for a CMS admin server.

Maintenance

ActivityActive
ResponsivenessResponsive

Resources