Sentry (local)
BetaSentry's MCP server reads issues, events and stack traces from Sentry.
- Developer Tools
- Local
- Runs
- On the developer's Mac
- Launched with
- npx, Docker
- Platform
- macOS
- Publisher
- Sentry
How it works
Every agent request passes through Ferentin policy before it reaches Sentry (local).
It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with npx -y @sentry/mcp-server or docker run -i --rm mcp/sentry.
Ferentin's endpoint agent finds Sentry (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.
- AI agentAsks for something
- Ferentin policies
- Sentry (local) MCP serverRuns on the developer's Mac
- Governed resultChecked, logged, returned
About Sentry (local)
Sentry's MCP server reads issues, events and stack traces from Sentry.
Frequently asked about Sentry (local)
- How do I connect Sentry (local) to Ferentin?
- Enroll your Macs with the Ferentin endpoint agent, then add Sentry (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
- Is the Sentry (local) integration generally available?
- The Sentry (local) integration is currently beta on Ferentin.
Related integrations
3
XcodeBuildMCP (local)
Sentry's XcodeBuildMCP builds, runs and tests iOS and macOS projects and manages simulators and devices through the developer's Xcode toolchain.
Sequential Thinking (local)
The reference structured-reasoning server. It is pure computation, with no network, credentials or file access.
Supabase (local)
Supabase's MCP server manages projects and queries databases with a personal access token.