Clearon Content Archive MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLEARON_CONTENT_ARCHIVE_ROOT | No | Overrides the archive storage location. | |
| CLEARON_CONTENT_ARCHIVE_WORKSPACE | No | Defines the root against which local artifact paths are validated. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_server_healthB | Report archive health, storage root, and non-publishing safety boundaries. |
| register_content_packageB | Create an append-only Clearon content record with local artifacts and editorial retrieval metadata. |
| get_content_recordA | Read a content snapshot and, by default, its complete append-only event history. |
| search_content_archiveC | Search archived titles, summaries, openings, topics, jurisdictions, and terminology. |
| find_content_recordB | Find exact archive records by content slug, WordPress post ID, or recorded publication/social URL. |
| update_content_artifactsC | Append a metadata or local-artifact update using optimistic revision control. |
| record_publicationB | Record a verified WordPress outcome. This tool never publishes and does not infer live state from a payload. |
| record_social_resultA | Record a LinkedIn or X outcome, including published URLs, schedules, queues, or blockers. This tool never posts. |
| record_source_correctionA | Append a provenance correction without rewriting the earlier archive history. |
| approve_voice_exampleB | Explicitly mark an exact archived excerpt as an approved Clearon voice example; never infers approval. |
| compare_payload_to_live_stateC | Compare a workspace-contained WordPress payload with a caller-supplied verified live-state response. |
| find_content_overlapB | Rank potentially overlapping archived content using disclosed lexical overlap; requires editorial review. |
| list_incomplete_follow_throughA | List records missing verified WordPress publication, featured-image verification, or completed LinkedIn/X outcomes. |
| list_update_candidatesA | List mechanically stale publications, post-publication source corrections, and image-verification gaps; does not make editorial recommendations. |
| generate_content_inventoryA | Generate a current structured inventory of archive, publication, social, topic, correction, and voice-example counts. |
| verify_archive_recordA | Replay an append-only event log and confirm whether it matches the stored snapshot without repairing it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
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.
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.
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.
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.