sentry
Provides integration with Sentry, allowing agents to search issues, events, and traces using Sentry's MCP endpoint.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@sentrysearch for unresolved issues in my-org"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
pi-sentry-mcp
Talk to Sentry from Pi. After you sign in, the agent can search issues, events, and traces on Sentry's MCP at https://mcp.sentry.dev/mcp.
You need Pi, pi-mcp-adapter, and a Sentry account.
Published as pi-sentry-mcp on npm. The pi-package keyword lists it on pi.dev/packages. Landing page: https://hempun10.github.io/pi-sentry-mcp/
Install
pi install npm:pi-mcp-adapter
pi install npm:pi-sentry-mcpRestart Pi or run /reload, then run /mcp-auth sentry and sign in in the browser.
pi-mcp-adapter stores the OAuth token. This repo never sees it.
If Pi says pi-mcp-adapter is not installed, install that package and reload.
Related MCP server: Sentry
Limit to one org or project
The default URL is https://mcp.sentry.dev/mcp. That can reach every org your account can access.
Put sentryMcp in .pi/settings.json for this project, or in ~/.pi/agent/settings.json for every project. .pi/settings.json overrides the user file.
Field | Required | Source | What it does |
| no | settings | Full MCP URL. Ignores organization and project. |
| no | settings or | Uses |
| no | settings or | Needs organization. Uses |
| no | settings or | Adds |
{
"sentryMcp": {
"organization": "my-org",
"project": "my-project"
}
}If you set project, you must also set organization.
Call it
The server name is sentry.
mcp({ search: "unresolved issues", server: "sentry" })
mcp({ tool: "search_issues", args: { organizationSlug: "my-org", query: "is:unresolved" } })Paste Sentry issue URLs as they are. Write org/project as organizationSlug/projectSlug.
Sentry lists tools at mcp.sentry.dev. Sentry can add or remove tools without a change in this repo.
What this repo does not do
It does not implement search_issues or other Sentry tools. Those run on Sentry's server.
It is not sentry-cli. It is not a self-hosted MCP. For self-hosted Sentry, set sentryMcp.url to your MCP endpoint.
Develop
npm install
npm run check
npm testLanding page:
cd site
npm install
npm run devSee CONTRIBUTING.md.
License
This server cannot be deployed
Maintenance
Related MCP Connectors
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
MCP server for Sentry - error monitoring, issue tracking, and debugging for AI assistants
Connect AI agents to Filepad workspaces through OAuth MCP.
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
Related MCP Servers
- FlicenseBqualityDmaintenanceEnables interaction with Sentry's error tracking platform to fetch and manage issue details, events, and project information through the Sentry API.452 npm1-
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Sentry's error tracking and monitoring tools through a unified API, allowing natural language access to Sentry services.MIT
- AlicenseNot gradedqualityAmaintenanceEnables interaction with Sentry organizations, projects, and issues directly from MCP clients like Claude Code.28 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables Claude Desktop to connect to a ServiceNow instance for debugging and monitoring through natural conversation.-