Sentry MCP Server
About
An MCP server for interacting with the Sentry error tracking and performance monitoring platform.
Details
- Author
- getsentry
- GitHub stars
- 11
- Downloads
- 388
- Categories
- Developer Tools, Other, Infrastructure
Jump to
- Lists all accessible Sentry projects for an organization.
- Resolves issue details using a short ID (e.g., PROJECT-123).
- Retrieves and analyzes specific Sentry events from an issue.
- Creates new projects in Sentry and returns client keys.
- Lists issues and events from a Sentry project or issue.
- Lists replays from a Sentry organization with filters.
- Supports summary or detailed views and plain or markdown output.
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Sentry MCP ServerCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install dependencies with npm install, then run the server with npx ts-node index.ts. Set the SENTRY_AUTH environment variable to your Sentry authentication token before starting. Configuration for Claude Desktop requires adding a JSON block to your Claude settings with the command and token.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"sentry mcp server": {
"sentry": {
"command": "npx",
"args": [
"ts-node",
"/Users/<your-user-directory>/sentry-mcp-ts/index.ts"
],
"env": {
"SENTRY_AUTH": "<YOUR_AUTH_TOKEN>"
}
}
}
}
}
McpServers
{
"sentry": {
"command": "npx",
"args": [
"ts-node",
"/Users/<your-user-directory>/sentry-mcp-ts/index.ts"
],
"env": {
"SENTRY_AUTH": "<YOUR_AUTH_TOKEN>"
}
}
}
Sentry MCP Server
A Model Context Protocol (MCP) server for interacting with Sentry. This MCP server provides tools to interact with the Sentry API, allowing AI assistants to retrieve and analyze error data, manage projects, and monitor application performance.
Requirements
- Node.js (v14 or higher)
- npm or yarn
- Sentry account with API access
- Sentry authentication token with appropriate permissions
Setup
1. Install dependencies:
npm install
Using this within an IDE
This MCP has been verified to work against Cursor, Codeium Windsurf, and Claude Desktop.
Using with Claude
To use this MCP server with Claude, add the following configuration to your Claude settings:
{
"mcpServers": {
"sentry": {
"command": "npx",
"args": ["ts-node", "/Users/<your-user-directory>/sentry-mcp-ts/index.ts"],
"env": {
"SENTRY_AUTH": "<YOUR_AUTH_TOKEN>"
}
}
}
}
Update with your directory path in the args field.
Replace <YOUR_AUTH_TOKEN> with your Sentry authentication token.
Available Tools
list_projects
Lists all accessible Sentry projects for a given organization.
Parameters:
- organization_slug (string, required): The slug of the organization to list projects from
- view (string, optional): View type, either "summary" or "detailed" (default: "detailed")
- format (string, optional): Output format, either "plain" or "markdown" (default: "markdown")
resolve_short_id
Retrieves details about an issue using its short ID.
Parameters:
- organization_slug (string, required): The slug of the organization the issue belongs to
- short_id (string, required): The short ID of the issue to resolve (e.g., PROJECT-123)
- format (string, optional): Output format, either "plain" or "markdown" (default: "markdown")
get_sentry_event
Retrieves and analyzes a specific Sentry event from an issue.
Parameters:
- issue_id_or_url (string, required): Either a full Sentry issue URL or just the numeric issue ID
- event_id (string, required): The specific event ID to retrieve
- view (string, optional): View type, either "summary" or "detailed" (default: "detailed")
- format (string, optional): Output format, either "plain" or "markdown" (default: "markdown")
list_error_events_in_project
Lists error events from a specific Sentry project.
Parameters:
- organization_slug (string, required): The slug of the organization the project belongs to
- project_slug (string, required): The slug of the project to list events from
- view (string, optional): View type, either "summary" or "detailed" (default: "detailed")
- format (string, optional): Output format, either "plain" or "markdown" (default: "markdown")
create_project
Creates a new project in Sentry and retrieves its client keys.
Parameters:
- organization_slug (string, required): The slug of the organization to create the project in
- team_slug (string, required): The slug of the team to assign the project to
- name (string, required): The name of the new project
- platform (string, optional): The platform for the new project
- view (string, optional): View type, either "summary" or "detailed" (default: "detailed")
- format (string, optional): Output format, either "plain" or "markdown" (default: "markdown")
list_project_issues
Lists issues from a specific Sentry project.
Parameters:
- organization_slug (string, required): The slug of the organization the project belongs to
- project_slug (string, required): The slug of the project to list issues from
- view (string, optional): View type, either "summary" or "detailed" (default: "detailed")
- format (string, optional): Output format, either "plain" or "markdown" (default: "markdown")
list_issue_events
Lists events for a specific Sentry issue.
Parameters:
- organization_slug (string, required): The slug of the organization the issue belongs to
- issue_id (string, required): The ID of the issue to list events from
- view (string, optional): View type, either "summary" or "detailed" (default: "detailed")
- format (string, optional): Output format, either "plain" or "markdown" (default: "markdown")
get_sentry_issue
Retrieves and analyzes a Sentry issue.
Parameters:
- issue_id_or_url (string, required): Either a full Sentry issue URL or just the numeric issue ID
- view (string, optional): View type, either "summary" or "detailed" (default: "detailed")
- format (string, optional): Output format, either "plain" or "markdown" (default: "markdown")
list_organization_replays
Lists replays from a specific Sentry organization.
Parameters:
- organization_slug (string, required): The slug of the organization to list replays from
- project_ids (string[], optional): List of project IDs to filter replays by
- environment (string, optional): Environment to filter replays by
- stats_period (string, optional): Time period for stats (e.g., "24h", "7d")
- start (string, optional): Start date for filtering replays
- end (string, optional): End date for filtering replays
- sort (string, optional): Field to sort replays by
- query (string, optional): Search query to filter replays
- per_page (number, optional): Number of replays per page
- cursor (string, optional): Cursor for pagination
- view (string, optional): View type, either "summary" or "detailed" (default: "detailed")
- format (string, optional): Output format, either "plain" or "markdown" (default: "markdown")
Running the Server
npx ts-node index.ts
Authentication
This tool requires a Sentry authentication token with appropriate permissions to access the Sentry API. You can generate a token in your Sentry account settings under Settings -> User Settings -> Auth Tokens.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.





