Read-only MCP diagnostics

Configure an application-scoped credential for release, decision and health diagnostics.

Updated 2026-09-15

On this page

Connect
Tools
Troubleshooting
Data boundaries

Read-only MCP diagnostics

Pakta exposes a read-only Model Context Protocol endpoint at /api/mcp. It combines release inventory, update decision replay and structured rollout telemetry for assistants that support Streamable HTTP.

Connect

Open Settings → MCP access in the console.
Create a credential, enter the client name, and select one or more applications. The default lifetime is 30 days.
Copy the token while it is shown. Pakta stores only a digest and never displays the full value again.
Configure your client with the endpoint https://<your-pakta-host>/api/mcp and an Authorization: Bearer <token> header.

The credential is application-scoped. Every application, channel, package, deployment and telemetry query is checked against that scope. Use an application ID or an exact name; an ambiguous name returns candidates instead of selecting one.

Tools

The server advertises these read-only tools:

Tool	Purpose
`auth_status`	Confirm the credential, expiry and application scope.
`list_apps`, `get_app_detail`	Inspect authorized applications and redacted configuration.
`list_channels`, `list_native_versions`	Inspect channel and native build catalogs.
`list_update_packages`, `list_deployments`	Inspect immutable packages and rollout targets.
`explain_update`	Replay the current update decision for client parameters. Replay does not consume SDK quota or write observations.
`get_patch_info`	Inspect exact-build patch jobs and pdiff mappings.
`get_request_observations`	Read privacy-preserving real check observations retained for seven days.
`get_rollout_health`, `get_adoption_trend`	Read event counts, time buckets and conservative heuristic guidance.
`diagnose_rollback`	Group structured rollback events by hash, version and channel.

List responses default to 50 items and cap at 100. Analysis defaults to the last 24 hours and accepts one or seven days, with optional channel, native package version and update hash filters. The health rules expose their sample denominators and thresholds; they never pause, roll back or publish a deployment.

Troubleshooting

401: send a Bearer header, check that the token was copied completely, and verify it has not expired or been revoked. API keys and browser session JWTs cannot authenticate the MCP endpoint.
403: check the request Origin and use the same host as the endpoint or an origin configured by the operator. A valid token cannot read an application outside its selected scope.
Unknown tool or invalid arguments: initialize the MCP client again so it discovers the current tool schema, then provide required fields such as application and packageVersion.

MCP is disabled by default until the operator sets MCP_ENABLED=true. The server accepts clients that support Streamable HTTP and a custom Bearer header; OAuth authorization is not part of this release.

Data boundaries

Real check observations contain application, channel, native build, SDK version, decision category and time. They exclude IP addresses, device identifiers, credentials and the original request. They are written asynchronously, retained for seven days, and may have a collection gap after the feature is enabled. Adoption values are event counts: mark_success means launch confirmation, not a deduplicated device adoption rate. Without crash stacks, rollback diagnosis cannot identify a crash root cause.