Report MCP config registration

Record that an MCP server entry was written for an agent runtime.

Called by jentic setup / jentic skill init once per runtime whose MCP config entry it wrote (best-effort on the CLI side — a failed report never blocks setup). Emits the mcp.config_registered internal event; when the operator opted into telemetry, the event is forwarded carrying at most the closed runtime tag. Reports are throttled per (actor, runtime) within a 24h in-process window — a throttled repeat is still a 202 with recorded: false, since the CLI treats the report as fire-and-forget. Any authenticated actor may report.

Request body

runtime'claude_desktop' | 'claude_code' | 'cursor' | 'codex' | 'other' required

Closed-enum tag naming the agent runtime an MCP config entry targets.

Attached only to mcp_config_registered — one event per runtime whose config file/entry jentic setup/jentic skill init writes. A closed set (never the raw runtime string) so the config-written → first-session → first-execute funnel stays property-free on the wire.

Example request

{
  "runtime": "cursor"
}

Response

Successful Response

recordedboolean required

Whether the report was recorded as an event. false means it was accepted but throttled (an identical (actor, runtime) report was already recorded within the last 24h).