Multi-portfolio Sentry MCP configuration generator with per-company isolation and clean handoff
Multi-portfolio Sentry MCP configuration generator with per-company isolation and clean handoff. The multi sentry mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.
Multi-org Sentry MCP configuration generator. Run multiple Sentry organizations simultaneously in Claude Desktop, Claude Code, or Cursor — each with isolated tokens, org-scoped sessions, and zero cross-org leakage.
@sentry/mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Everything the assistant can do here goes through one of these:
org — readproject — readteam — readevent — writeField — Requireddisplay_name — Yessentry_org_slug — Yessentry_project_slug — Notoken_env_var — Yesai_search — Yesactive — Yesskills — NoYou will need 3 environment variables: SENTRY_ACCESS_TOKEN, EMBEDDED_AGENT_PROVIDER, ANTHROPIC_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Multi Sentry MCP's toolset — org, project, team and 11 more — is a fair guide to whether it matches your workflow. It is maintained by ideacraftershq; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| org | read |
| project | read |
| team | read |
| event | write |
| Field | Required |
| display_name | Yes |
| sentry_org_slug | Yes |
| sentry_project_slug | No |
| token_env_var | Yes |
| ai_search | Yes |
| active | Yes |
| skills | No |
| Skill | Default |
| inspect | ON |
{
"mcpServers": {
"sentry-acme-web": {
"command": "npx",
"args": [
"@sentry/mcp-server@latest",
"--organization-slug=acme-web",
"--project-slug=acme-web-app"
],
"env": {
"SENTRY_ACCESS_TOKEN": "${SENTRY_TOKEN_ACME_WEB}",
"EMBEDDED_AGENT_PROVIDER": "anthropic",
"ANTHROPIC_API_KEY": "${ANTHROPIC_API_KEY}"
}
},
"sentry-widgets-inc": {
"command": "npx",
"args": [
"@sentry/mcp-server@latest",
"--organization-slug=widgets-inc",
"--project-slug=widgets-api"
],
"env": {
"SENTRY_ACCESS_TOKEN": "${SENTRY_TOKEN_WIDGETS_INC}",
"EMBEDDED_AGENT_PROVIDER": "anthropic",
"ANTHROPIC_API_KEY": "${ANTHROPIC_API_KEY}"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SENTRY_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| EMBEDDED_AGENT_PROVIDER | Configuration value read at startup. | Optional |
| ANTHROPIC_API_KEY | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.