@cvcm/mcp

Unified local MCP runtime and integration installer for CVCM.

It is designed for individual developers and small teams who want coding agents to reuse relevant project knowledge and prove a patch against the repository's own local Docker command before returning it. The repository stays on the developer's machine; Docker evidence is a local engineering gate, not remote execution attestation.

npm install -g @cvcm/mcp
export CVCM_API_TOKEN="deployment-issued-token"
cvcm auth import-env

During an interactive install, CVCM asks once:

Automatically publish sanitized Docker-PASS solutions to shared probation under MIT? [y/N]

Answering y enables automatic publication of sanitized, Docker-verified patches for projects without an explicit .cvcm.json. The answer is stored locally with restrictive permissions and is not asked again for the same policy version. CI and non-interactive installs default to No. Only choose yes for code you have the right to redistribute under MIT. An explicit .cvcm.json always overrides this global policy.

Codex launches cvcm mcp locally (the installer performs best-effort client registration when Codex is available). The process keeps workspace baselines, patch construction, Docker execution, and private verification records on the user's machine. It uses Bearer authentication only for the configured shared memory API. The installer stores the token in ~/.config/cvcm/token with mode 0600; agent configuration contains the API URL, not the token. Restart the agent after setup.

cvcm auth status
CVCM_API_TOKEN="rotated-token" cvcm auth import-env

Native agent flow

memory_search                 approved memory, once per task
workspace_begin               exact complete task, before edits
edit existing project files
workspace_verify              one authoritative local Docker command
workspace_abandon             user-cancelled/replaced task, private audit reason
  |- no install consent -> PASS + publication_status=SKIPPED
  `- install consent -> PASS + automatic review/submit when ticket is APPROVED
solution_submit               explicit fallback when automatic publication is disabled/deferred
memory_feedback               optional untrusted advisory reuse telemetry

cvcm workspace-begin --task "exact complete user task" \
  --repository /path/to/repository
cvcm workspace-verify BASELINE_ID --repository /path/to/repository
cvcm workspace-abandon BASELINE_ID --reason "user replaced this task" \
  --repository /path/to/repository
cvcm solution-submit VERIFICATION_ID \
  --repository /path/to/repository \
  --task "the same exact complete user task"

A successful local Docker result stays PASS regardless of remote publication_status. SKIPPED, MANUAL_REVIEW, REJECTED, or UNAVAILABLE means only that no submission ticket exists; it is not a reason to rewrite locally correct code. Only compliance APPROVED includes the short-lived ticket required by solution_submit.

When remote compliance is enabled, the ticket binds the sanitized task, patch, relevant_context, public evidence digests, stack, license, and consent policy. Provenance remains client-claimed and is not ticket-bound. Stack metadata is secret-scanned, and private/unsafe workspace paths are omitted from the bounded filename inventory. Remote compliance and shared-memory submission are separate opt-ins; installation enables neither.

Search is attempted once per task. Empty results and network errors are final for that task. workspace_begin returns existing filenames that the agent should inspect before creating parallel files. The verifier uses an already available local image with --pull=never; an environment failure should be fixed in the image, command, or fixture without changing requested behavior.

cvcm doctor --repository /path/to/repository checks credential storage, API readiness, Docker, and the configured verifier image without exposing tokens. cvcm demo creates a temporary project and proves the local Docker path end to end. cvcm metrics reads a private per-repository aggregate only; it performs no telemetry upload.

New repositories need no preliminary setup command: workspace_begin infers a local profile from common manifests and reports its bound command/image. It does not create .cvcm.json. Add that file only to override the inferred profile or to explicitly opt out of the install-time publication policy.

memory_feedback accepts an approved solution, outcome, and full SHA-256 local verification digest. Exact replay is idempotent and conflicting replay is rejected. It is untrusted advisory telemetry and does not modify trust_score, reuse counters, or search ranking.

Repository policy and commit capture

cvcm init /path/to/repository
# review and edit .cvcm.json
cvcm install-hook /path/to/repository

remoteComplianceConsent, redistributionAllowed, userConsent, and autoSubmit are false by default unless the one-time install consent is enabled. Post-commit candidates remain local under .cvcm/pending unless all required publication controls are true. The automatic policy applies only to inferred project profiles; an explicit .cvcm.json remains authoritative. Changing the verification command/image, stack, license, or consent after verification invalidates submission.

Agent setup

cvcm clients
cvcm setup agy --scope user
cvcm setup claude --scope user
cvcm setup cursor --scope project --project /path/to/repository
cvcm setup all --dry-run

All supported agents use the same local MCP runtime. Installers merge supported JSON configuration without replacing unrelated servers, create a one-time .cvcm-backup, and refuse conflicting or unsupported files. See the repository integration reference for the authoritative client, tool, authentication, and HTTP contracts.