Jam MCP
OFFICIAL SERVERHosted Jam server that feeds bug recordings, logs and network traffic to coding agents
Sentry's own server for debugging with Sentry issues, events, traces and docs from a coding agent
Official · Sentry JavaScript Remote (hosted) · Streamable HTTPLocal · stdio DevOps and monitoringDeveloper tools
95 popularity score ★ 958 ↓ 247k/wk
Opens the app, which asks before it adds the server. Then replace each <NAME> in its settings with your value.
claude mcp add --transport http sentry https://mcp.sentry.dev/mcp/<ORGANIZATION_SLUG>/<PROJECT_SLUG>{
"mcpServers": {
"sentry": {
"url": "https://mcp.sentry.dev/mcp/<ORGANIZATION_SLUG>/<PROJECT_SLUG>"
}
}
}{
"servers": {
"sentry": {
"type": "http",
"url": "https://mcp.sentry.dev/mcp"
}
}
}Opens the app, which asks before it adds the server. Then replace each <NAME> in its settings with your value.
It needs SENTRY_AUTH_TOKEN. Replace each <NAME> with your value.
claude mcp add sentry -e SENTRY_AUTH_TOKEN=<SENTRY_AUTH_TOKEN> -- npx -y @sentry/mcp-server@latest{
"mcpServers": {
"sentry": {
"command": "npx",
"args": [
"-y",
"@sentry/mcp-server@latest"
],
"env": {
"SENTRY_AUTH_TOKEN": "<SENTRY_AUTH_TOKEN>"
}
}
}
}{
"mcpServers": {
"sentry": {
"command": "npx",
"args": [
"-y",
"@sentry/mcp-server@latest"
],
"env": {
"SENTRY_AUTH_TOKEN": "<SENTRY_AUTH_TOKEN>"
}
}
}
}{
"servers": {
"sentry": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@sentry/mcp-server@latest"
],
"env": {
"SENTRY_AUTH_TOKEN": "<SENTRY_AUTH_TOKEN>"
}
}
}
}[mcp_servers.sentry]
command = "npx"
args = ["-y", "@sentry/mcp-server@latest"]
[mcp_servers.sentry.env]
SENTRY_AUTH_TOKEN = "<SENTRY_AUTH_TOKEN>"gemini mcp add --scope user -e SENTRY_AUTH_TOKEN=<SENTRY_AUTH_TOKEN> sentry npx -- -y @sentry/mcp-server@latestSENTRY_AUTH_TOKEN secret |
Required: Sentry user auth token; wins over a stored login. Can be left out after `npx -y @sentry/mcp-server auth login`. SENTRY_ACCESS_TOKEN is the deprecated old name. |
|---|---|
SENTRY_HOST |
Optional: Hostname of a self-hosted Sentry; drops the seer skill from the defaults. |
SENTRY_URL |
Optional: Full Sentry URL instead of SENTRY_HOST; an http:// URL allows a self-hosted host without TLS. |
MCP_SKILLS |
Optional: Comma-separated skills to grant, e.g. inspect,triage; all active skills when unset. |
MCP_DISABLE_SKILLS |
Optional: Comma-separated skills to turn off, e.g. project-management. |
SENTRY_CLI_NO_TELEMETRY |
Optional: Set to 1 to stop the server reporting its errors and traces to Sentry (DO_NOT_TRACK=1 works too). |
| Set together: llm | |
EMBEDDED_AGENT_PROVIDER |
Optional: openai, azure-openai, anthropic or openrouter; set it with the matching key. |
OPENAI_API_KEY secret |
Optional: Key when the provider is openai. |
ANTHROPIC_API_KEY secret |
Optional: Key when the provider is anthropic. |
OPENROUTER_API_KEY secret |
Optional: Key when the provider is openrouter. |
OPENAI_MODEL |
Optional: Model override for the OpenAI provider. |
ANTHROPIC_MODEL |
Optional: Model override for the Anthropic provider. |
Sentry MCP is Sentry's own MCP server. It sits between an assistant and the Sentry API and is built for coding agents such as Cursor and Claude Code, so most of its tools serve debugging. An agent can search errors, logs, traces, metrics, profiles and replays, read an issue with its stack trace and breadcrumbs, update or annotate it, link it to an outside ticket, and start a Seer analysis. Other tools set up teams, projects and client keys (DSNs), or create, change and delete alert rules and cron, uptime and metric monitors. It can also search Sentry's documentation.
The catalog in the code holds 79 tools. Two are deprecated aliases (get_ai_conversation_details, search_ai_conversations), and search_events is now marked deprecated in favour of one search tool per dataset. Fourteen tools are listed to the client directly. The rest are reached through search_sentry_tools and execute_sentry_tool, a gateway the code calls a temporary fallback while full listing rolls out. Skills such as inspect, triage, seer and project-management decide which tools are on offer.
Sentry runs it as a hosted service at https://mcp.sentry.dev/mcp, where you sign in with OAuth. The address can be narrowed to one organization or project (/mcp/{organizationSlug}/{projectSlug}), so tools default to it.
The local version is the npm package @sentry/mcp-server, and it is the way to reach self-hosted Sentry. The package is now the Sentry CLI's `sentry mcp` command bundled into one file. It takes a user auth token in SENTRY_AUTH_TOKEN, or a login made once with `npx -y @sentry/mcp-server auth login`, which the `sentry` CLI shares. Plain-language search needs an OpenAI, Azure OpenAI, Anthropic or OpenRouter key. Without one, those tools take Sentry query syntax only.
| To run it yourself | Node.js 22.15+ |
|---|---|
| Runs on | macOS, Windows, Linux |
| Sentry | Free tiersentry.io account or a self-hosted Sentry; self-hosted needs the local version |
| OpenAI, Azure OpenAI, Anthropic or OpenRouter | Paid planoptional: only for the plain-language translation in the search tools |
For the local version, create a Sentry user auth token with org:read, project:read, project:write, team:read, team:write and event:write, and pass it as SENTRY_AUTH_TOKEN. Instead you can run `npx -y @sentry/mcp-server auth login` once in a terminal. The server only starts that sign-in itself when stdin is a terminal, so a client-launched server with no token and no stored login exits with an error. For self-hosted Sentry set SENTRY_HOST, or an http:// SENTRY_URL for a host without TLS.
Suits developers on sentry.io who want a coding agent to look into production errors, traces and issues and act on them, and who are happy to sign in with OAuth to Sentry's hosted endpoint. Scoping the address to one project keeps the tool set small. Teams on self-hosted Sentry need the local version with a token, and lose Seer unless they opt back in and their install runs it. Its tools can update issues and change projects, teams and client keys, and some delete alert rules and monitors, so narrow it with skills (inspect alone, say) when the assistant should only read. Anyone running it locally who wants nothing sent to Sentry should set SENTRY_CLI_NO_TELEMETRY=1.
37 only read, 18 change things, 5 can delete or overwrite.
find_organizationsfind_projectsupdate_issue changessearch_errorssearch_logssearch_tracessearch_metricssearch_profilessearch_replaysanalyze_issue_with_seer changessearch_issuesget_sentry_resourcesearch_sentry_toolsexecute_sentry_tool changessearch_eventswhoamifind_teamsfind_releasesfind_dashboardsfind_monitorscreate_monitor changesdelete_monitor_environment deletesfind_uptime_monitorscreate_uptime_monitor changesupdate_uptime_monitor changesdelete_uptime_monitor deletesfind_metric_monitorscreate_metric_monitor changesupdate_metric_monitor changesdelete_metric_monitor deletesfind_alert_rulesget_alert_rulecreate_alert_rule changesupdate_alert_rule changesdelete_alert_rule deletesget_issue_detailsget_event_stacktraceget_issue_activityget_issue_breadcrumbssearch_issue_eventssearch_attributesfind_dropped_eventsadd_issue_note changeslink_issue changesunlink_issue deletesget_trace_detailsget_replay_detailsget_profilesearch_agent_conversationsget_agent_conversation_detailscreate_team changescreate_project changesupdate_project changesadd_team_to_project changescreate_dsn changesfind_dsnssearch_docsget_docget_snapshotsubmit_feedback_to_sentry_team changes