Skip to main content
Glama
Clearon Content Archive MCP

Clearon Content Archive MCP

by kwgoodwin

Clearon Content Archive MCP

MCP server for append-only content records, verified publication history, social follow-through, and retrieval-friendly metadata.

It is designed to preserve provenance and workflow state without publishing anything itself.

What it does

  • Stores append-only content events per slug.

  • Maintains a materialized snapshot for fast reads and repairs stale snapshots from the durable event log during normal reads.

  • Records verified WordPress and social outcomes.

  • Tracks source corrections without rewriting earlier history.

  • Provides overlap search, inventory, and follow-through reporting.

  • Verifies whether event history exactly matches the stored snapshot.

  • Finds records by exact slug, current post ID, and current or historical recorded publication/social URLs.

Related MCP server: What Brandon Thinks Chat MCP

What it does not do

  • It does not publish to WordPress or social platforms.

  • It does not treat a payload marked publish as proof of live publication.

  • It does not make legal or editorial truth determinations.

  • It does not allow artifact paths outside the configured workspace.

Requirements

  • Node.js 20 or newer

  • A local MCP client that can launch a stdio server

Installation

cd tools/clearon-content-archive-mcp
npm install
npm test
npm run smoke

MCP client setup

Example stdio configuration:

{
  "mcpServers": {
    "clearon-content-archive": {
      "command": "node",
      "args": ["/absolute/path/to/clearon-content-archive-mcp/server.mjs"],
      "env": {
        "CLEARON_CONTENT_ARCHIVE_WORKSPACE": "/absolute/path/to/workspace"
      }
    }
  }
}

Use CLEARON_CONTENT_ARCHIVE_WORKSPACE to define the root against which local artifact paths are validated. Override the archive storage location with CLEARON_CONTENT_ARCHIVE_ROOT.

Storage

By default, archive data is stored outside the repository in a user data directory:

  • macOS: ~/Library/Application Support/clearon-content-archive-mcp/content-archive

  • Linux: ${XDG_DATA_HOME:-~/.local/share}/clearon-content-archive-mcp/content-archive

  • Windows: %APPDATA%\\clearon-content-archive-mcp\\content-archive

Each record lives under records/<slug>/ and stores:

  • events.jsonl

  • snapshot.json

Verification and repair

verify_archive_record is read-only. It compares the rebuilt event history to the stored snapshot and reports whether they match.

Automatic repair runs on normal record reads and mutation paths so a stale materialized snapshot does not hide a newer durable event.

The package audit CLI is:

npm run audit

It reports verification failures explicitly instead of silently skipping them.

  1. Register the local draft package.

  2. Append verified publication or update results.

  3. Append LinkedIn and X outcomes, including blockers or skips.

  4. Record provenance corrections as new events.

  5. Use overlap and search tools before drafting related work.

  6. Use inventory and incomplete-follow-through output during audits.

  7. Run verification after migration, manual recovery, or suspected corruption.

Tools

  • get_server_health

  • register_content_package

  • get_content_record

  • search_content_archive

  • find_content_record

  • update_content_artifacts

  • record_publication

  • record_social_result

  • record_source_correction

  • approve_voice_example

  • compare_payload_to_live_state

  • find_content_overlap

  • list_incomplete_follow_through

  • list_update_candidates

  • generate_content_inventory

  • verify_archive_record

URL handling

Stored URLs must use http or https, and URL credentials are rejected.

Because archive history is append-only, avoid writing sensitive URLs with tokens or other secrets in query strings.

Development

npm test
npm run smoke
npm run syntax
npm run audit

Available Tools

16 tools
approve_voice_exampleB

Explicitly mark an exact archived excerpt as an approved Clearon voice example; never infers approval.

Inputs: slug (required), excerpt (required), expected_revision (required), note, +1 more.

compare_payload_to_live_stateC

Compare a workspace-contained WordPress payload with a caller-supplied verified live-state response.

Inputs: slug (required), live_state (required), payload_path.

find_content_overlapB

Rank potentially overlapping archived content using disclosed lexical overlap; requires editorial review.

Inputs: slug (required), limit.

find_content_recordB

Find exact archive records by content slug, WordPress post ID, or recorded publication/social URL.

Inputs: url, slug, post_id.

generate_content_inventoryA

Generate a current structured inventory of archive, publication, social, topic, correction, and voice-example counts.

Inputs: no named parameters.

get_content_recordA

Read a content snapshot and, by default, its complete append-only event history.

Inputs: slug (required), include_events.

get_server_healthB

Report archive health, storage root, and non-publishing safety boundaries.

Inputs: no named parameters.

list_incomplete_follow_throughA

List records missing verified WordPress publication, featured-image verification, or completed LinkedIn/X outcomes.

Inputs: no named parameters.

list_update_candidatesA

List mechanically stale publications, post-publication source corrections, and image-verification gaps; does not make editorial recommendations.

Inputs: older_than_days.

record_publicationB

Record a verified WordPress outcome. This tool never publishes and does not infer live state from a payload.

Inputs: slug (required), status (required), expected_revision (required), url, +10 more.

record_social_resultA

Record a LinkedIn or X outcome, including published URLs, schedules, queues, or blockers. This tool never posts.

Inputs: slug (required), status (required), platform (required), expected_revision (required), +7 more.

record_source_correctionA

Append a provenance correction without rewriting the earlier archive history.

Inputs: slug (required), field (required), reason (required), previous_value (required), +4 more.

register_content_packageB

Create an append-only Clearon content record with local artifacts and editorial retrieval metadata.

Inputs: slug (required), title (required), content_type (required), topics, +6 more.

search_content_archiveC

Search archived titles, summaries, openings, topics, jurisdictions, and terminology.

Inputs: query, topic, jurisdiction.

update_content_artifactsC

Append a metadata or local-artifact update using optimistic revision control.

Inputs: slug (required), expected_revision (required), note, title, +7 more.

verify_archive_recordA

Replay an append-only event log and confirm whether it matches the stored snapshot without repairing it.

Inputs: slug (required), include_rebuilt_snapshot.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, such as searching, exact lookup, and registering content. The main ambiguity is between list_incomplete_follow_through and list_update_candidates, which both surface records needing verification or correction, but their descriptions largely clarify the intended focus.

    Naming Consistency5/5

    All tool names use a consistent lower_snake_case verb_noun pattern, such as get_content_record, record_publication, and approve_voice_example. Even the longer compound names like compare_payload_to_live_state and list_incomplete_follow_through follow the same predictable action-first convention.

    Tool Count4/5

    The server has 16 tools, which is slightly above the typical well-scoped range, but each tool appears to support a distinct archival lifecycle concern. The count is not excessive given the breadth of content, publication, social, correction, and voice-example workflows being covered.

    Completeness4/5

    The tool set covers the core content archive lifecycle: register, read, search, update, verify, and append publication/social/correction outcomes. Minor gaps exist, such as no explicit unpublish or approval-revocation tool, but the append-only design and existing verification tools make those acceptable omissions.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers