Skip to main content
Glama
Sign In
Paperboy CMS

Paperboy CMS

Official
by hybriden
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Paperboy CMS

  • agent-cms

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

Related Servers

  • ledric

    ledricofficial

    getledric
    A
    license
    Not graded
    quality
    D
    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
    D
    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.
    2 npm
    4
    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.6/5.0

Scored across 25 tools

Disambiguation4/5

Most tools target distinct resources and actions (content vs assets vs versions), but a few pairs overlap: list_content vs list_tree both list pages, update_content vs set_field both edit drafts, and upload_asset vs create_upload_link both add assets. Descriptions explicitly differentiate when to use each, so misselection is unlikely but possible.

Naming Consistency5/5

All names use snake_case with a leading verb (list_, get_, create_, update_, etc.), and the noun patterns are predictable across content, asset, and version tools. Minor forms like assist_writing (verb + gerund) remain readable and do not break the overall convention.

Tool Count4/5

25 tools is on the heavy side for a single server, but the domain is broad—content lifecycle, assets, versions, sites, and AI writing—and each tool covers a distinct operation without obvious redundancy. Slightly over the typical 3–15 range, but justified for a full CMS API.

Completeness4/5

Core content lifecycle is thoroughly covered: create/read/update/publish/unpublish/trash/restore, versioning, locale variants, and asset upload/delete/alt text. Minor gaps exist—no direct asset file replacement, no text search for content, and no schema or site write operations—but these are either out of scope or workable via list operations.

Maintenance

ActivityActive
ResponsivenessOutdated data

Resources