Labsco
getsentry logo

Sentry MCP

✓ Official★ 751

from getsentry

Official Sentry MCP server for investigating issues, error reports, traces, and performance monitoring data from AI coding agents.

🔥🔥🔥🔥✓ VerifiedAccount requiredAdvanced setup
#automation#cloud#devops#git#monitoring#translation

sentry-mcp

Sentry's MCP service is primarily designed for human-in-the-loop coding agents. Our tool selection and priorities are focused on developer workflows and debugging use cases, rather than providing a general-purpose MCP server for all Sentry functionality.

This remote MCP server acts as middleware to the upstream Sentry API, optimized for coding assistants like Cursor, Claude Code, and similar development tools. It's based on Cloudflare's work towards remote MCPs.

Local Development

To contribute changes, you'll need to set up your local environment:

  1. Set up environment and agent skills:

    Copy & paste — that's it
    make setup-env  # Creates .env files and installs shared agent skills

    This also runs npx @sentry/dotagents install to install shared skills from getsentry/skills into .agents/skills/ (symlinked into .claude/skills and .cursor/skills). If you need to update skills later, run it directly:

    Copy & paste — that's it
    npx @sentry/dotagents install

  2. Create an OAuth App in Sentry (Settings => API => Applications):

    • Homepage URL: http://localhost:5173
    • Authorized Redirect URIs: http://localhost:5173/oauth/callback
    • Note your Client ID and generate a Client secret

  3. Configure your credentials:

    • Edit .env in the root directory and add either OPENAI_API_KEY or OPENROUTER_API_KEY
    • Edit packages/mcp-cloudflare/.env and add:
      • SENTRY_CLIENT_ID=your_development_sentry_client_id
      • SENTRY_CLIENT_SECRET=your_development_sentry_client_secret
      • COOKIE_SECRET=my-super-secret-cookie

  4. Start the development server:

    Copy & paste — that's it
    pnpm dev

Verify

Run the server locally to make it available at http://localhost:5173

Copy & paste — that's it
pnpm dev

To test the local server, enter http://localhost:5173/mcp into Inspector and hit connect. Once you follow the prompts, you'll be able to "List Tools".

Tests

There are three test suites included: unit tests, evaluations, and manual testing.

Unit tests can be run using:

Copy & paste — that's it
pnpm test

Evaluations require a .env file in the project root with some config:

Copy & paste — that's it
# .env (in project root)
OPENAI_API_KEY=      # Use OpenAI-backed AI-powered tools
OPENROUTER_API_KEY=  # Or use OpenRouter-backed AI-powered tools

Note: The root .env file provides defaults for all packages. Individual packages can have their own .env files to override these defaults during development.

Once that's done you can run them using:

Copy & paste — that's it
pnpm eval

Manual testing (preferred for testing MCP changes):

Copy & paste — that's it
# 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"

Note: The CLI defaults to http://localhost:5173. Override with --mcp-host or set MCP_URL environment variable.

Comprehensive testing playbooks:

  • Stdio testing: See docs/testing/stdio.md for complete guide on building, running, and testing the stdio implementation (IDEs, MCP Inspector)
  • Remote testing: See docs/testing/remote.md for complete guide on testing the remote server (OAuth, web UI, CLI client)

Development Notes

Automated Code Review

This repository uses automated code review tools (like Cursor BugBot) to help identify potential issues in pull requests. These tools provide helpful feedback and suggestions, but we do not recommend making these checks required as the accuracy is still evolving and can produce false positives.

The automated reviews should be treated as:

  • ✅ Helpful suggestions to consider during code review
  • ✅ Starting points for discussion and improvement
  • ❌ Not blocking requirements for merging PRs
  • ❌ Not replacements for human code review

When addressing automated feedback, focus on the underlying concerns rather than strictly following every suggestion.

Contributor Documentation

Looking to contribute or explore the full documentation map? See CLAUDE.md (also available as AGENTS.md) for contributor workflows and the complete docs index. The docs/ folder contains the per-topic guides and tool-integrated .md files.