Merge Unified's Sentry integration Merge Agent Handler's Sentry MCP server

Connect your AI Agents to Sentry in minutes

Merge lets you securely connect your agents to Sentry and thousands of tools instantly

Start building for free

Read docs

Sentry

Learn more about Merge Agent Handler

Available tools

get_event

Get event details by organization, project, and event ID.

get_latest_event

Get the most recent event for an issue.

get_oldest_event

Get the first occurrence of an issue.

list_issues

List project issues with optional filtering. In 'query', combine conditions by listing them as space-separated filters (e.g. 'is:unresolved level:error'); all listed filters must match. The boolean keywords OR and AND are not supported and will error. To match alternative values, call this tool once per value and combine the results.

get_issue

Get issue details by ID.

update_issue

Update issue status, assignment, or bookmarks.

delete_issue

Delete an issue permanently.

bulk_update_issues

Bulk update multiple issues in a project.

bulk_delete_issues

Bulk delete issues by query.

list_issue_events

List all events for an issue.

list_organizations

List all organizations accessible to the authenticated user.

get_organization

Get organization details by slug.

update_organization

Update organization name or slug.

list_project_keys

List project client keys (DSNs).

create_project_key

Create a new project client key.

get_project_key

Get project key details.

update_project_key

Update project key settings.

delete_project_key

Delete a project key permanently.

list_projects

List all projects accessible to the user.

list_organization_projects

List organization projects.

get_project

Get project details.

create_project

Create a new project under a team.

update_project

Update project settings.

delete_project

Delete a project permanently.

list_releases

List organization releases with filtering.

create_release

Create a new release for deployment tracking.

get_release

Get release details by version.

update_release

Update release metadata.

delete_release

Delete a release permanently.

list_release_commits

List release commits.

get_project_stats

Get project event statistics over time.

get_organization_stats

Get organization-wide event statistics.

list_project_tags

List project tags with statistics.

get_tag_values

Get tag values with occurrence counts.

list_teams

List organization teams.

get_team

Get team details.

create_team

Create a new team

update_team

Update team settings.

delete_team

Delete a team permanently.

list_organization_members

List organization members.

get_user

Get organization member details.

validate_credential

Validate Sentry credentials. Verifies credentials during setup.

View all tools by creating a free account See more tools

How to set up Merge Agent Handler

In an mcp.json file, add the configuration below, and restart Cursor.

Learn more in the official documentation ↗

1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11

Copy Code

Open your Claude Desktop configuration file and add the server configuration below. You'll also need to restart the application for the changes to take effect.

Make sure Claude is using the Node v20+.

Learn more in the official documentation ↗

1{
2  "mcpServers": {
3    "agent-handler": {
4      "command": "npx",
5      "args": [
6        "-y",
7        "mcp-remote@latest",
8        "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
9        "--header",
10        "Authorization: Bearer ${AUTH_TOKEN}"
11      ],
12      "env": {
13        "AUTH_TOKEN": "yMt*****"
14      }
15    }
16  }
17}

Copy Code

Open your Windsurf MCP configuration file and add the server configuration below.
Click on the refresh button in the top right of the Manage MCP server page or in the top right of the chat box in the box icon.

Learn more in the official documentation ↗

1{
2    "mcpServers": {
3      "agent-handler": {
4        "command": "npx",
5        "args": [
6          "-y",
7          "mcp-remote@latest",
8          "https://ah-api.merge.dev/api/v1/tool-packs/<tool-pack-id>/registered-users/<registered-user-id>/mcp",
9          "--header",
10          "Authorization: Bearer ${AUTH_TOKEN}"
11        ],
12        "env": {
13          "AUTH_TOKEN": "<ah-production-access-key>"
14        }
15      }
16    }
17  }

Copy Code

In Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows), run "MCP: Open User Configuration".

You can then add the configuration below and press "start" right under servers. Enter the auth token when prompted.

Learn more in the official documentation ↗

1{
2  "inputs": [
3    {
4      "type": "promptString",
5      "id": "agent-handler-auth",
6      "description": "Agent Handler AUTH_TOKEN", // "yMt*****" when prompt
7      "password": true
8    }
9  ],
10  "servers": {
11    "agent-handler": {
12      "type": "stdio",
13      "command": "npx",
14      "args": [
15        "-y",
16        "mcp-remote@latest",
17        "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
18        "--header",
19        "Authorization: Bearer ${input:agent-handler-auth}"
20      ]
21    }
22  }
23}

Copy Code

FAQs on using Merge's Sentry MCP server

What is a Sentry MCP server?

It’s an MCP server that exposes data and functionality from Sentry via tools. Your agents can use these tools to update issues, list issues created within a certain timeframe, bulk delete old issues, and more.

You can use Sentry’s official MCP server or one that’s provided by a 3rd-party, like Merge.

How can I use the Sentry MCP server?

Here are some common use cases:

Automated issue triage and routing: When a new Sentry issue appears, your agent can classify it and assign it to the right team or on-call, based on ownership rules and recent history

Create an incident “packet” for on-call: Your agent can pull the error, stack trace, release version, and recent deploy context from Sentry, and then post a clean summary into Slack or an incident channel with suggested next steps

Detect release regressions and roll back faster: After a deploy, your agent can monitor new spikes in errors tied to the release, identify top new issues, and trigger a rollback recommendation or open a “release regression” ticket automatically

Duplicate and noise reduction: Your agent can review new issues, compare them to existing ones, and auto-merge duplicates or mark noisy issues for de-prioritization, keeping the queue clean

Performance and latency troubleshooting: Your agent can watch Sentry performance traces for slow endpoints, identify the worst offenders, and file a weekly “top regressions” report with suggested owners

What are popular tools for Sentry’s MCP server?

Here are some popular tools across data types:

Issues

<code class="blog_inline-code">list_issues</code>
<code class="blog_inline-code">get_issue</code>
<code class="blog_inline-code">update_issue</code>
<code class="blog_inline-code">delete_issue</code>

Organizations

<code class="blog_inline-code">get_organization</code>
<code class="blog_inline-code">update_organization</code>
<code class="blog_inline-code">list_organizations</code>

Releases

<code class="blog_inline-code">create_release</code>
<code class="blog_inline-code">list_release_commits</code>
<code class="blog_inline-code">get_release</code>
<code class="blog_inline-code">update_release</code>

What makes Merge Agent Handler’s Sentry MCP server better than alternative Sentry MCP servers?

Merge Agent Handler's Sentry MCP server offers rich, platform-level capabilities:

Managed authentication and credential handling: Agent Handler guides users through authentication and securely manages credentials for connected tools

Enterprise-grade security and DLP: Tool inputs and outputs are scanned for sensitive data, with configurable rules to block, redact, or mask data

Real-time observability and auditability: Every tool call is logged with a fully-searchable audit trail for debugging, monitoring, and compliance

Evaluation Suite for reliability: Test and validate Sentry tool behavior before deploying to production, so your team can ship higher-quality connectors and a more consistent end-user experience

Can I set custom security rules for Sentry tool calls in Merge Agent Handler?

Yes, Merge Agent Handler includes a security gateway with data loss protection (DLP) that lets you apply default or custom rules to tool inputs and responses. These rules can block, redact, or mask sensitive data during agent-initiated tool calls, including those to Sentry.

Here are some examples of rules you can set:

Redact PII from Sentry issue descriptions and comments. If a tool call attempts to write an email address, phone number, SSN-like pattern, or credit card-like pattern into an issue description or comment, automatically redact it

Mask customer identifiers when reading Sentry events. When a tool retrieves event payloads, stack traces, request bodies, or user context, mask fields like user.id and any internal customer ID patterns before returning results to your agent

Limit writes to Sentry to approved projects only. Deny any tool call that creates or updates issues outside an allowlist of Sentry project slugs or project IDs (this is useful when you have multiple environments or customer-specific projects)

Enforce “no external links” in issue content. Block issue/comment writes that include non-allowlisted domains. For example, prevent agents from pasting links to unapproved pastebins or file-sharing sites into Sentry issues

How can I start using Merge Agent Handler’s Sentry MCP server?

You can follow these steps:

1. Create or log into your Merge Agent Handler account.

2. Create a Tool Pack for the workflow you want (for example, “Incident triage” or “Release monitoring”). Tool Packs define which connectors and tools your agent can access.

3. Add the Sentry connector to that Tool Pack and choose the tools you want exposed (for example, read-only tools for investigation, plus write tools if you want the agent to create/update issues).

4. Create a Registered User for the identity your agent will act as (end user or service account). This is the container that holds credentials used for tool execution.

5. Authenticate Sentry for that Registered User using Agent Handler’s managed authentication flow, so credentials are stored and handled securely

6. Copy the MCP endpoint URL for your Tool Pack and Registered User and paste it into your MCP client.

7. Run a few test tool calls, then verify behavior using Agent Handler’s logs/audit trail and observability views.

8. (Optional) Add security/DLP rules for Sentry tool calls (block, redact, or mask sensitive data) before using it in production.