# CARBON MCP server

The CARBON MCP server exposes the current local verification surface to
MCP-compatible coding agents.

## What it provides

- project and change analysis;
- local planning, generation, execution, and results;
- browser-capability negotiation for approved local controllers;
- durable test-intent and evidence management;
- focused quality-domain workflows;
- confidence planning, evaluation, review, release, and incident support;
- durable human decision context for missing intent, consequence, domain, and accountability oracles;
- private local feedback workspaces and an optional separately deployed private reviewer queue;
- protected local settings and credential handling;
- Jira/Xray and TestRail evidence integrations with guarded write previews;
- branded local progress and result artifacts.

The server keeps planned, observed, inferred, blocked, skipped,
`NOT ASSESSED`, and `NOT MEASURED` states distinct. It does not expose raw
passwords or API keys to the coding agent.

Use `carbon_get_capabilities` for current discovery and `carbon_settings` for
the protected local settings surface.

## Human decision context API

`carbon_human_context` has five local actions:

- `generate` inspects the project and durable CARBON evidence, then persists a
  small ranked question set.
- `status` returns the open/answered summary and confidence qualifier.
- `answer` stores one explicit human answer by `HUM-*` ID, either as free text
  or a returned quick-option ID, with an optional comment.
- `comment` stores a note against a `HUM-*` question or the overall project.
- `report` republishes the durable branded context snapshot.

`generate`, `answer`, and `comment` return an in-agent CARBON Human workspace
link as well as the durable report. The protected local workspace supports
one-click answer starters and comments; every change is recorded to
`.carbon/human/decision-context.json` for future agent work.

The server never infers an answer from silence. It does not send answers to a
cloud service. Open questions qualify confidence and guide later planning; they
do not turn technical evidence into a failure or prevent a technical confidence
assessment from being produced.

## Private feedback API

`carbon_feedback_context` keeps feedback in
`.carbon/feedback/requests.json` and has these local actions:

- `create` makes a scoped request for a URL, image, document, API, code
  surface, or other artifact and opens the protected Feedback workspace.
- `status` returns local requests, responses, and non-secret delivery state.
- `respond` and `comment` save explicit local human feedback.
- `sync` retrieves only the returned responses for one request from the
  explicitly reconfirmed private service, then records them as project-local
  qualitative context.
- `report` republishes the branded durable feedback snapshot.

When the request includes an explicitly configured `privateServiceUrl`,
recipient, one-time `privateServiceKey`, and `privateServiceConfirmed=true`,
CARBON submits it to the bundled self-hosted `feedback-service/`. It never
sends feedback to a public CARBON or provider cloud, never persists that key,
and never treats a queued invitation as received feedback. The external
service sends a rich email link to its protected web form; it does not use
unreliable embedded email forms.
