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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/kwgoodwin/clearon-content-archive-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server