@sentry/mcp-server weekly downloads statistics

sentry-mcp

This is a prototype of an MCP server, acting as a middleware to the upstream Sentry API provider.

This package is primarily for running the stdio MCP server. If you do not know what that is, or do not need it, we suggest using the public remote service:

Note: Some tools require additional configuration: • AI-powered search tools (search_events and search_issues): These tools use OpenAI to translate natural language queries into Sentry's query syntax. They require an OPENAI_API_KEY environment variable. Without this key, these specific tools will be unavailable, but all other tools will function normally.

Authorization

The MCP server uses a skills-based authorization system that maps user-friendly capabilities to technical API permissions.

Available Skills

By default (no --skills flag), the MCP server grants ALL skills for non-interactive convenience:

• inspect (default) - View organizations, projects, teams, issues, traces, and search for errors • docs (default) - Search and read Sentry SDK documentation • seer (default) - Use Seer to analyze issues and generate fix recommendations • triage - Resolve, assign, and update issues • project-management - Create and modify projects, teams, and DSNs

Customizing Skills

You can limit which skills are granted using the --skills flag:

Constraint-Based Tool Exclusion

When a session is scoped to a specific organization or project (tenant-bound context), certain list tools are automatically excluded since they cannot query other resources:

• find_organizations is hidden when the session is constrained to a specific organization (organizationSlug constraint) • find_projects is hidden when the session is constrained to a specific project (projectSlug constraint)

This ensures that only relevant tools are available in constrained contexts. When constraints are not set, all tools are available based on your granted skills.

Environment Variables

You can also use environment variables:

If SENTRY_HOST is not provided, the CLI automatically targets the Sentry SaaS endpoint. Configure this variable only when you operate a self-hosted Sentry deployment.

Note: Command-line flags override environment variables.

Required Sentry Token Scopes

To utilize the stdio transport, create a User Auth Token in Sentry with these scopes:

Minimum (read-only): • org:read, project:read, team:read, event:read

Additional (for write operations): • event:write - Required for triage skill • project:write, team:write - Required for project-management skill

The MCP server will automatically request the appropriate scopes based on your granted skills.

Migration from Scopes (Deprecated)

⚠️ Deprecated: The --scopes and --add-scopes flags are deprecated. Use --skills instead.

If you're currently using scopes:

The host configuration accepts two distinct formats:

• SENTRY_HOST: Hostname only (no protocol) • Examples: sentry.example.com, sentry.internal.example.com, localhost:8000

Note: Only HTTPS connections are supported for security reasons.

By default we also enable Sentry reporting (traces, errors) upstream to our cloud service. You can disable that, or send it to a different Sentry instance by using the --sentry-dsn flag:

Description from the npm listing.