Sentry's Model Context Protocol (MCP) server is designed for human-in-the-loop coding agents, focusing on developer workflows and debugging use cases. It acts as middleware to the Sentry API, optimized for coding assistants like Cursor, Claude Code, and similar development tools.
The easiest way to get started is to visit the deployed service:
The stdio transport is the simplest way to use the MCP with a self-hosted Sentry installation:
Create a User Auth Token in Sentry with the following scopes:
Launch the transport using npx:
npx @sentry/mcp-server@latest --access-token=sentry-user-token
npx @sentry/mcp-server@latest --access-token=sentry-user-token --host=sentry.example.com
You can also configure the MCP server using environment variables:
SENTRY_ACCESS_TOKEN=your_token_here
SENTRY_HOST=sentry.example.com # Optional for self-hosted deployments
OPENAI_API_KEY=your_openai_key # Required for AI-powered search tools
For testing the service, you can use the MCP Inspector:
pnpm inspector
Enter the MCP server URL (http://localhost:5173) and hit connect to trigger the authentication flow.
The CLI provides a convenient way to interact with the MCP server:
# Test with local dev server (default: http://localhost:5173)
pnpm -w run cli "who am I?"
# Test agent mode (use_sentry tool only)
pnpm -w run cli --agent "who am I?"
# Test against production
pnpm -w run cli --mcp-host=https://mcp.sentry.dev "query"
# Test with local stdio mode (requires SENTRY_ACCESS_TOKEN)
pnpm -w run cli --access-token=TOKEN "query"
The AI-powered search tools (search_events and search_issues) require an OpenAI API key to translate natural language queries into Sentry's query syntax.
If you have issues with OAuth flow when accessing the inspector on 127.0.0.1, try using localhost instead by visiting http://localhost:6274.
The CLI defaults to http://localhost:5173. You can override this with the --mcp-host flag or by setting the MCP_URL environment variable.
The Sentry MCP server provides tools for:
Connect to the server using the MCP Inspector or CLI to see the complete list of available tools.
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "sentry-mcp" '{"command":"npx","args":["@sentry/mcp-server@latest"]}'
See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:
{
"mcpServers": {
"sentry-mcp": {
"command": "npx",
"args": [
"@sentry/mcp-server@latest"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.json2. Add this to your configuration file:
{
"mcpServers": {
"sentry-mcp": {
"command": "npx",
"args": [
"@sentry/mcp-server@latest"
]
}
}
}
3. Restart Claude Desktop for the changes to take effect