Skip to main content
Glama
kwgoodwin

Clearon Editorial Pipeline MCP

by kwgoodwin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Clearon Editorial Pipeline MCP

No user-submitted related servers found.

    Related Servers

    • Clearon WordPress MCP

      kwgoodwin
      A
      license
      B
      quality
      C
      maintenance
      Enables controlled WordPress publishing through the WordPress REST API with dry-run validation, source-audit gating, safe write/rollback, media upload, scheduling, and duplicate-post resolution.
      13
      MIT

    • clearon-source-audit

      kwgoodwin
      A
      license
      B
      quality
      C
      maintenance
      Enables revision-bound source audits with exact article fingerprinting, claim-to-source mapping, quotation verification, and immutable JSON evidence reports for prepublication review.
      9
      MIT

    • WordPress Blog MCP

      stef-k
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to inspect a WordPress blog, reuse existing media and taxonomy, prepare and update drafts, and publish only after explicit human approval through a narrow, auditable interface.
      MIT

    • FluxProof

      equinoxaifinance-rgb
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables evidence-bearing change monitoring for public text pages, providing normalized diffing, SHA-256 hashing, and signed webhook notifications.
      -

    • vibelore

      fbwndrud
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI hosts to plan, draft, and check long-form novel chapters while honoring canon settings, character state, arcs, and check ordering, with approval-gated atomic commits. It keeps world, character, and chapter files as the human-editable source of truth, with snapshots and rollback for recovery.
      Apache 2.0
    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

    A3.5/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each tool targets a distinct action in the editorial workflow, and the descriptions generally clarify the resource being acted on. The only mild ambiguity is between audit_revision and propose_revision, since both involve style heuristics, but the existing-versus-proposed distinction is made clear.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern, such as get_editorial_project, propose_revision, and export_wordpress_payload. There are no mixed conventions or vague generic verbs.

    Tool Count5/5

    Nine tools is well-scoped for an editorial pipeline covering project creation, inspection, revision workflow, approval, and export. Each tool maps to a meaningful stage in the process without redundancy or bloat.

    Completeness4/5

    The core lifecycle—create, list, get, audit, propose, apply, approve, and export—is covered with no dead ends. Missing operations like project metadata updates or explicit rejection are minor given the immutable-revision design and the intentional dry-run export boundary.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources