Concord MCP for Paperclip
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Concord MCP for Paperclip
A small, self-hosted coordination bridge for MCP clients and Paperclip workers. It gives short-lived batch agents durable task context, bounded Q&A, verified artifact snapshots and an explicit review boundary. Paperclip remains the execution authority; optional real Concord MCP integration projects task metadata into a shared local workspace.
Status: experimental v0.5.0. Native Codex receipt, fixed executor review handoff, conservative disposition recovery and opt-in synthetic acceptance are available. Live normal/recovery trials reached Done unattended; a failing-test trial was rejected. Completion uses a separately provisioned, exact-manifest owner-policy capability. See the live report. See native receipt deployment and E2E recipe. A new production readiness fix was also received, independently tested, reviewed through MCP and finalized without operator intervention; see the 0.3.1 real-code acceptance. The Codex–Antigravity cooperation trial was resumed in its existing tasks after an infrastructure outage. Two real peer questions/answers influenced the implementation and integration tests; all four batches reached native Done and bridge complete after independent review. The public example passes 51 tests. Version 0.3.2 corrects receipt of an explicitly bound Process retry; site telemetry must support the corresponding optional run ID. Cooperation remains mediated by an active supervisor for code review. Version 0.4.0 adds opt-in, root-scoped pre-provider recovery in the existing receiver, a durable one-shot intent and actual-successor reconciliation after lost responses. Unknown effects, auth/quota and paused profiles remain blocked. See the recovery design and acceptance report.
Version 0.5.0 adds opt-in receipt of partial code after a verified final-response limit. The existing receiver snapshots allowlisted files before a separate root capability clears the exact terminated profile's error. Native failure stays failed; partial files never become a full result or authorize a model retry. See 480-second recovery.
Trusted verifier-policy changes can be reloaded within a long-lived MCP session; identity/authority drift still requires restart. The original failing chat channel was recovered without restarting the app. See policy reload and the guarded operator handoff. A real project module has passed the complete worker, receipt, independent sandbox and operator-review path. See v0.2, test evidence and limitations before enabling execution.
Polish project brief and archive
See the one-page A4 brief, project purpose and provenance, unattended Codex acceptance, historical Codex pilot, native receipt protocol and archive map. Version 0.3.0 adds a separate native Codex receiver and formal review handoff. General results await coordinator review; only preapproved, exact-hash synthetic fixtures may be accepted by the trusted opt-in policy.
Related MCP server: Codex Control Plane MCP
Why this exists
A message addressed to a process that already exited cannot wake that process. A batch worker needs durable questions, an answer and verified partial files in a later bounded attempt. A successful process exit also does not establish that its files were reviewed, integrated or deployed.
This project separates those concerns:
MCP tools queue scoped work without browser sessions or model-selected identities.
A SQLite WAL journal retains intents and exact-file/directory claims.
Non-idempotent remote creates are quarantined after ambiguous outcomes.
A dedicated Paperclip
task_bridgeidentity is restricted to a project and an explicit assignee allowlist.Paperclip's native Process adapter supplies a real run identity for audited mutations. A local Unix broker retains the persistent credential.
Artifact collection snapshots only allowlisted regular files; independent review is an explicit operator attestation against a manifest digest.
Concord is an optional metadata projection through its official MCP interface.
Quick start
Python 3.11+ and uv are required for development.
uv sync --extra dev --locked
uv run ruff check src tests
uv run pytest -q
uv buildCopy examples/bridge.example.json to a private configuration directory, supply
your own IDs and credential reference, then run:
uv run paperclip-bridge --config /absolute/private/bridge.json doctor
uv run paperclip-bridge --config /absolute/private/bridge.json serveserve uses the official Python MCP SDK and stdio. It opens no HTTP listener.
Authenticate the process through the OS or a restricted SSH command. Do not
expose this stdio service through an unauthenticated network wrapper.
Without native_agent_id, submissions stay in the local queue until an operator
runs drain. drain creates unassigned backlog issues and never runs models.
Dispatch is a separate operation with recent trusted readiness evidence.
MCP tools
Tool | Purpose |
| Capabilities, identity and remote health |
| Sanitized roster; idle is not proof of readiness |
| Idempotently queue bounded synthetic/public work |
| Read journal and authoritative Paperclip status |
| Bounded wait for a local version change |
| Record task Q&A; does not claim live model delivery |
| Read a verified snapshot received by the trusted collector |
| Receive existing terminal runs and independent verification |
| Prepare a linked continuation with partial files |
| Attest review and queue final task status |
Worker configuration, arbitrary file collection, run evidence and policy changes
are deliberately absent from the model-facing tools. Those are operator CLI
operations. Worker-to-worker cooperation is mediated by the coordinator; a
worker cannot grant itself delegation authority. An optional receive-only systemd
timer observes existing runs after the chat ends. It never creates model work,
rotates accounts or deploys code. Native Codex receive-cycle additionally applies
a disabled-by-default, pre-submit exact-content acceptance policy for reviewed
synthetic fixtures and wakes only the non-model coordinator to finalize them.
Read architecture, security, deployment, API contract and rollback.
Upstream relationship
This is an independent MIT-licensed adapter, not an official Concord or
Paperclip product. No upstream source is bundled. The real Concord integration
was checked against Get-Concord-AI/concord-mcp 0.16.0, commit
f00d7c812ff708979b1784c48b0201096bc8bad5.
Private deployment material
site-private/ is a locally maintained, Git-ignored directory for deployment
configuration, internal inventory and operator notes. It is not included in
source or wheel distributions. Store actual secrets in an OS keychain or secret
manager; a reference to a secret is not the secret itself.
Version0.4.1 routes gateway traffic through the bounded process-group runner. The real transport/cooperation acceptance records a90second receiver SSH interruption, automatic recovery and reviewed artifacts, including the preserved failed Antigravity acknowledgement.
paperclip_partial_artifacts(task_id, include_content=false) reads the separate
partial receipt. A partial task needs a new reviewed integration result; it
cannot pass paperclip_review_work as a successful full manifest.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Shared task queue for humans and AI agents: leases, handoffs, approvals and signed receipts.
Project management shared by people and AI agents, with persistent project state through MCP.
MCP protocol requiring task acceptance and provenance tags. Self-hosted only - see README.
Headless task management for bots, apps and AI agents. Remote MCP server, OAuth or access token.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables agents to submit and manage persistent, dependency-aware task graphs with immutable artifacts, resource reservations, durable event streaming, and retryable process execution over MCP.12MIT
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to submit long-running Codex Desktop tasks as durable asynchronous operations, poll their status, handle approvals and Plan Mode workflows, and retrieve final reports without holding calls open. It also provides retry-safe submission, restart recovery, queue and worker status, diagnostics, and repair for local Codex automation.-
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI coding providers to run structured multi-agent workflows with documents, tracked tasks, handoffs, and health-gated task lifecycle management over MCP.29 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to claim, heartbeat, submit, split, park, and resume atomic work-queue tasks, with fencing tokens and receipts, while storing and versioning records and content-addressed files through MCP.1MIT