MCP
Report MCP config registration
Changed onRecord 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.
post/mcp/config-registrations
Request
- Base URL: / (relative, and the document was published on a file host, not at the API’s origin)
- URL: /mcp/config-registrations
- Auth: one of:
- HTTP bearer
- OAuth 2 (authorization code, authorization URL /authorize, token URL /oauth/token)
Request body
Example request
{
"runtime": "cursor"
}Response
Successful Response
Example response
{
"recorded": true,
"runtime": "cursor"
}Changes
- info
the endpoint scheme security
OAuth2was added to the API
- info
- info
endpoint added
- info