Connect a coding agent

Your agent reads PostDeploy through the MCP server or the HTTP API. You approve each connection and choose what it can do.

MCP server

The MCP URL is https://postdeploy.dev/mcp.

Claude Code

claude mcp add --transport http postdeploy https://postdeploy.dev/mcp

Codex

codex mcp add postdeploy --url https://postdeploy.dev/mcp

If Codex does not open the browser by itself, run:

codex mcp login postdeploy

Other MCP clients

Add the server to the client's MCP configuration:

{
  "mcpServers": {
    "postdeploy": {
      "type": "http",
      "url": "https://postdeploy.dev/mcp"
    }
  }
}

The same text is on the organization settings page, ready to copy.

Approve the connection

Your client registers with PostDeploy and opens a browser window.
Sign in. The page shows the client, its host, your account and the organization.
Choose the access. Read access to issues, logs and projects is selected by default.
Approve. The client gets a token for that organization only.

The connection then appears under Connected agents in the organization settings, with the time it was last used. Revoke it there when you no longer need it.

Access scopes

Scope	Allows	Who can grant it
`issues:read`	View the issue inbox, event details, and stack traces.	Any member
`issues:triage`	Resolve, ignore, and reopen issues.	Owners and admins
`logs:read`	Search logs and follow a live tail.	Any member
`projects:read`	View projects and sources.	Any member
`projects:write`	Create projects, sources, and ingestion keys.	Owners and admins
`reports:write`	Publish an investigation report.	Any member
`deployments:write`	Record a deployment of a project, for example from CI.	Owners and admins

API keys

Use an API key for CI or for a client without OAuth. Create one in the organization settings. A new key has read access to issues, logs and projects unless you choose other scopes. It expires after 30 days unless you choose a shorter or longer period, up to 90 days.

PostDeploy shows the key once. Send it as a bearer token to the HTTP API or the MCP server:

Authorization: Bearer YOUR_API_KEY

Keys stop working when they expire, when you revoke them, when their owner resets the password or leaves the organization, and when the organization is deleted. A key that holds a scope for owners and admins loses that scope when its owner loses the role.

Example investigation

A short investigation of a new error, with the MCP tools in the order an agent calls them:

list_issues          {"status": "open"}
get_error_context    {"issue_id": 41}
list_deployments     {"project_id": 3}
compare_deployment   {"deployment_id": 7}

get_error_context returns one event with its stack, the deployment that was live at the time, and at most 50 related logs. Logs match on the event's trace ID, then its request ID, then its service and release. The response says which match it used.

compare_deployment counts error events per minute in equal windows before and after a deployment. It shows that two things happened together in time. Your agent still needs the stack and logs to explain a cause.