MCP Server Sentry
Enables querying and analyzing error reports and events from Sentry, including retrieving issue details with stack traces, status, timestamps, and event counts via the Sentry error tracking service.
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., "@MCP Server Sentryget details for issue SENTRY-12345"
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.
MCP Server Sentry - TypeScript Implementation
This is a Model Context Protocol (MCP) server implemented in TypeScript for connecting to the Sentry error tracking service. This server allows AI models to query and analyze error reports and events on Sentry.
Features
get_sentry_issueToolRetrieves and analyzes Sentry issues by ID or URL
Input:
issue_id_or_url(string): Sentry issue ID or URL to analyze
Returns: Issue details including:
Title
Issue ID
Status
Level
First seen timestamp
Last seen timestamp
Event count
Complete stack trace
sentry-issuePrompt TemplateRetrieves issue details from Sentry
Input:
issue_id_or_url(string): Sentry issue ID or URL
Returns: Formatted issue details as conversation context
Related MCP server: Sentry MCP Server
Installation
# Install dependencies
npm install
# Build the project
npm run buildConfiguration
The server is configured using environment variables. Create a .env file in the project root directory:
# Required: Sentry authentication token
SENTRY_AUTH_TOKEN=your_sentry_auth_token
# Optional: Sentry organization name
SENTRY_ORGANIZATION_SLUG=your_organization_slug
# Optional: Sentry project name
SENTRY_PROJECT_SLUG=your_project_slug
# Optional: Sentry base url
SENTRY_BASE_URL=https://sentry.com/api/0Alternatively, you can set these environment variables at runtime.
Running
Run the server via standard IO:
node dist/index.jsDebug with MCP Inspector:
npx @modelcontextprotocol/inspector node dist/index.jsEnvironment Variables Description
SENTRY_AUTH_TOKEN(required): Your Sentry API access tokenSENTRY_PROJECT_SLUG(optional): The slug of your Sentry projectSENTRY_ORGANIZATION_SLUG(optional): The slug of your Sentry organization
The latter two variables can be omitted if project and organization information are provided in the URL.
License
This project is licensed under the MIT 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.
A Model Context Protocol server for Wix AI tools
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Related MCP Servers
- FlicenseBqualityDmaintenanceA Model Context Protocol server that retrieves and analyzes Sentry.io issues, allowing users to inspect error reports, stacktraces, and debugging information from their Sentry account.222-
- FlicenseBqualityFmaintenanceA Model Context Protocol server that enables AI assistants to interact with Sentry for error tracking and monitoring, allowing retrieval and analysis of error data, project management, and performance monitoring through the Sentry API.1121-
- AlicenseNot gradedqualityDmaintenanceA TypeScript server that allows AI agents to access, retrieve, and analyze Sentry error data through the Modern Context Protocol.252MIT

Sentry MCP Serverofficial
FlicenseBqualityFmaintenanceA Model Context Protocol server that lets AI assistants interact with the Sentry API to retrieve and analyze error data, manage projects, and monitor application performance.1111-