# Build a Sentry agent with Claude Code

> Have Claude Code build a Sentry agent with the Agent200 SDK: managed OAuth, ready-made tools and one API key.

- Page: https://www.agent200.com/tools/sentry/framework/claude-code/
- Connector: [Sentry](https://www.agent200.com/tools/sentry.md)
- Framework: Claude Code
- Updated: 2026-11-15

## Instructions for AI agents

Goal: connect Sentry to Claude Code with Agent200.
Guide: https://www.agent200.com/tools/sentry/framework/claude-code/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Make sure Sentry is enabled for the project in the Agent200 dashboard (Connectors), with the endpoints and scopes the task needs.
3. Add the Agent200 SDK to the project and create a client with that key.
4. Give every request a stable id for the end user. Agent200 uses only that user's own connections.
5. Connect the user's Sentry account through Agent200. If Agent200 returns an authorization link, show it to the user and continue once they have approved access on Sentry.
6. Run requests through Agent200 with a model (for example openai/gpt-5.6-sol) and "sentry" in the tools. The model decides when a Sentry tool is needed; Agent200 executes the call.
7. Check it works with this request: "What are the top unresolved errors in the API project this week"
   What should come back:
   - An answer in `result.output`, built from the user's own Sentry data.
   - Behind the scenes, the model calls a Sentry tool, such as `sentry_list_projects`, and Agent200 runs it.
8. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Sentry, then retry.

The code on the guide page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

## Overview

This guide has Claude Code build a Sentry agent with the Agent200 SDK, in your own project. When you finish, your agent can call the Sentry tools for each of your users.

Claude Code writes the code from the steps below; Agent200 runs the Sentry calls with each user's own connection and handles the OAuth flow and the tokens. You do not build or maintain a Sentry integration.

- **Connector:** [Sentry](https://www.agent200.com/tools/sentry/)
- **Works with:** Claude Code · Coding agent, with the SDK
- **Authentication:** Managed OAuth, per end user
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [5 tools](https://www.agent200.com/tools/sentry/framework/claude-code/#tools)
- **Model in examples:** `openai/gpt-5.6-sol`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **Sentry enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **An end user with a Sentry account.** They approve access once, on Sentry's own page.
- **Claude Code in your project.** It writes the code with the Agent200 SDK; you review it.

## Connect Sentry to Claude Code

### Step 1: Create your Agent200 API key

Open the API keys page in the Agent200 dashboard and choose Create an API key. Copy the key and store it as an environment variable, AGENT200_API_KEY, or in your secrets manager. One key covers Sentry and every other connector and model enabled for your project. Keep it out of chats, prompts and source control.

Create an API key: https://agent200.com/platform/apikeys/

File `.env`:

```bash
# Keep the key out of your code, prompts and chats.
export AGENT200_API_KEY="paste-your-key-here"
```

(Conceptual example of the Agent200 SDK.)

### Step 2: Give this guide to Claude Code

Start Claude Code in your project and paste the agent brief from this page, or give it the address of this guide's Markdown version. Claude Code follows the steps below in order: the SDK, the Sentry connection and the first request. Review the code it writes before you run it.

### Step 3: Set up the Agent200 SDK

Add the SDK to your project and create a client with the key from the environment.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 4: Let your user connect Sentry

Each end user authorizes their own Sentry account once, through managed OAuth. If the user has not connected yet, Agent200 returns an authorization link: show it to them, and they approve access on Sentry's own page. Agent200 handles the callback, stores the tokens and refreshes them.

File `connect.js`:

```js
// Each end user authorizes their own Sentry account, once.
const connection = await agent200
  .user("user_123")
  .connect("sentry");

if (connection.authorizationUrl) {
  // Show this link to your user; Agent200 handles the rest.
  console.log(connection.authorizationUrl);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 5: Run with the Sentry tools

Name the user, the model and Sentry in the tools. The model decides when a Sentry tool is needed, and Agent200 executes the call with the user's own connection.

File `run.js`:

```js
const result = await agent200
  .user("user_123")
  .run({
    model: "openai/gpt-5.6-sol",
    input: "What are the top unresolved errors in the API project this week",
    tools: ["sentry"],
  });

console.log(result.output);
```

(Conceptual example of the Agent200 SDK.)

## Test your connection

Ask: "What are the top unresolved errors in the API project this week"

What should come back:

- An answer in `result.output`, built from the user's own Sentry data.
- Behind the scenes, the model calls a Sentry tool, such as `sentry_list_projects`, and Agent200 runs it.

If Agent200 returns an authorization link instead, the user has not connected Sentry yet. Go back to the connect step.

## Sentry tools Claude Code can call

- **List projects** (`sentry_list_projects`, read): List the projects in an organization.
- **List issues** (`sentry_list_issues`, read): List a project's issues, filtered by a search query and time range.
- **Get an issue** (`sentry_get_issue`, read): Read an issue's details, status and event counts.
- **Get the latest event** (`sentry_get_latest_event`, read): Read the most recent event of an issue, with its stack trace and tags.
- **Update an issue** (`sentry_update_issue`, write): Resolve, ignore or assign an issue.

## How it works

1. **Your app sends the request.** It calls Agent200 with the model, instructions, the input, the end user's id and the Sentry tools.
2. **The model picks a tool.** The model decides whether a Sentry tool is needed, and with which arguments.
3. **Agent200 runs the call.** It uses that user's own Sentry connection, within the endpoints and scopes your project allows, and returns the result to the model.
4. **Your app gets the result.** Agent200 returns the completed result. Your app decides when the agent runs and what happens next.

**Each user's own connection.** Connections belong to individual end users. A request for one user never reaches another user's Sentry account.

**Permissions at every level.** Your project settings decide what the agent may request, the end user decides what they authorize, and Sentry enforces what its API grants.

## Troubleshooting

### The request says Sentry authorization is required

The end user has not connected Sentry yet, or the connection needs to be approved again. Agent200 returns an authorization link: show it to the user, let them approve access on Sentry's own page, then run the request again.

### Claude Code does not use the Sentry tools

Check that Sentry is enabled for your project in the dashboard's Connectors settings and that it is in the tools you send with the request. Naming Sentry in the request, or in the instructions, also helps the model choose the right tool.

### A tool call is refused or returns less than expected

Agent200 runs only what your project allows (services, endpoints and scopes), and Sentry returns only what the end user authorized. Widen the endpoints or scopes in the dashboard if the agent needs more, then ask the user to connect Sentry again so they can approve the new access.

### The results come from the wrong account

Every request names an end user (`user_123` in the examples). Pass the id of the person your agent is working for: Agent200 then uses only that user's Sentry connection, never another user's.

### The API key was pasted into a chat or committed

Create a new key on the [API keys page](https://agent200.com/platform/apikeys/), update `AGENT200_API_KEY` wherever your app reads it, and stop using the old one. Keep keys in environment variables or a secrets manager, never in prompts, chats or source control.

## Use Sentry with another framework

- [Sentry + Claude](https://www.agent200.com/tools/sentry/framework/claude.md)
- [Sentry + ChatGPT](https://www.agent200.com/tools/sentry/framework/chatgpt.md)
- [Sentry + Muse](https://www.agent200.com/tools/sentry/framework/muse.md)
- [Sentry + Grok Bot](https://www.agent200.com/tools/sentry/framework/grok-bot.md)
- [Sentry + OpenAI Dots](https://www.agent200.com/tools/sentry/framework/openai-dots.md)
- [Sentry + Claude Duet](https://www.agent200.com/tools/sentry/framework/claude-duet.md)
- [Sentry + Hermes Agent](https://www.agent200.com/tools/sentry/framework/hermes-agent.md)
- [Sentry + OpenClaw](https://www.agent200.com/tools/sentry/framework/openclaw.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
