Your coding agent can read your code. Now it can read production.

Change one DSN and your Sentry SDK sends errors and logs to PostDeploy. Your agent then reads the stack trace, the payload and the matching logs over MCP.

Start 14-day free trial See agent setup

No credit card. $449 per year per organization after the trial.

~/checkoutSample data.
$ claude mcp add --transport http postdeploy https://www.postdeploy.dev/mcp
> get_error_context event_id=7f3a9c1e5b2d4860a1c3e5f7092b4d6e q=checkout
TypeError: Cannot read properties of undefined
at applyCoupon (src/cart/coupon.ts:88)
related 12 logs match "checkout"
correlation text match only; not causal
> search_logs q=coupon scope=recent
logs 3 lines, first at 14:06 UTC

Your agent works from whatever you paste.

When production breaks, you copy a stack trace from one tab, search logs in another and paste both into the chat. The agent sees only what you remembered to copy.

If you run ops yourself, this work is yours, and a client may be waiting for your answer.

One tool call returns the evidence.

get_error_context returns one stored error with its stack and payload. Give it a search term and it adds the logs that match. The result labels that match as text correlation, so your agent cannot present it as a cause.

How it works

  1. Change one DSN.

    Create a project and a source, then point your Sentry SDK at the new DSN. A test event checks the path before you deploy. Read the quickstart.

  2. Connect your agent.

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

    Sign in through your browser. Check the organization and approve read access. Connections cannot change data.

  3. Ask what broke.

    Copy an event ID from the Issues page and give it to your agent. The agent reads the error, then searches the logs for what it needs.

  1. You

    Checkout has been throwing errors since this afternoon. The event ID is 7f3a9c1e5b2d4860a1c3e5f7092b4d6e. What happened?

  2. Agent
    get_error_context {"event_id":"7f3a9c1e5b2d4860a1c3e5f7092b4d6e","q":"checkout"} TypeError at applyCoupon (src/cart/coupon.ts:88), 12 related logs, correlation: text match only search_logs {"q":"coupon","scope":"recent"} 3 lines: cart has no promo code, first at 14:06 UTC
  3. Agent

    The stack stops at coupon.ts:88, which reads coupon.code with no check. The logs show carts without a promo code reach that line. The log match is text only, so check this against the code before you ship a fix.

Sample data. The tool calls and fields are real. The reasoning is your agent's.

Capabilities

  • Keep your Sentry SDK.

    PostDeploy accepts a standard DSN. To leave, change the DSN back.

  • A dashboard for you, too.

    Read issues, stack traces and logs for each project without an agent.

  • One DSN for each environment.

    Production and staging each get a source and a DSN of their own.

  • Your agent can only read.

    The MCP tools cannot change data. OAuth access reads one organization and expires after one hour.

$449 per year for one organization, every feature included.

Error events
1 million per month
Logs
100 GB per month
Retention
Errors 90 days, logs 90 days
Projects and members
Unlimited

Over a monthly allowance, PostDeploy refuses new data until the next month. It never bills overages.

Without a subscription after the trial, ingestion stops. You can read stored data until it expires.

Credentials are redacted before storage. PostDeploy runs on Cloudflare Workers and stores archived payloads in Cloudflare R2. One person builds and runs it.

Start 14-day free trial See pricing Privacy

Change one DSN and ask your agent what broke.

Start 14-day free trial

No credit card. Email and password only.