Connect a coding agent

Connect your agent to read issues and logs for one organization.

Connect through MCP

claude mcp add --transport http postdeploy https://www.postdeploy.dev/mcp
codex mcp add postdeploy --url https://www.postdeploy.dev/mcp
codex mcp login postdeploy

Approve access

  1. Let the client register and open your browser.
  2. Sign in. Select an organization if required.
  3. Check the client name, callback host, account, and organization.
  4. Approve read access to issues, logs, and projects.

Each connection has this fixed set of read scopes. Access expires after one hour. Connect again when access expires.

The server supports public clients, dynamic registration, authorization codes, and PKCE with S256. It does not issue refresh tokens.

Read the metadata at /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server.

Use the tools

context.get {"q":"cart"}
search_logs {"q":"cart","scope":"archived","limit":50}
get_error_context {"event_id":"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa","q":"cart"}

Copy an event ID from the Issues page for event_id. Supply project_id when event IDs occur in multiple projects.

Log correlation uses text only. It does not prove a cause. Deployment comparison is unavailable.

Revoke access

Send a form request to POST /oauth/revoke. Include token and client_id to revoke that token.

To revoke all your grants for a client in the current organization, send client_id with your session cookie and same-origin Origin header.

Other members cannot revoke your grants. The dashboard has no connection controls.

Keep ingest keys separate

Use a DSN only to send events. OAuth access works only at /mcp. It cannot create projects or DSNs.