Observability. MCP servers, the command line and skills for connecting an agent to Sentry.
Official server
1 server
Sourced servers by others
5
Command line
sentry-cli
Vendor skills
none
Official server
Published by Sentry's owner: we named it as the system's official server after reading its registry record, or it is published under Sentry's own domain. See what first-party means.
No known vulnerability in the listed npm and PyPI versions, from OSV on . That is what OSV lists, not a review of the code.
Command line
sentry-cli is a command-line tool for Sentry. For an agent that runs on your machine and has a shell, a command-line tool can be the simpler choice: there is no server to connect, and no tool definitions take room in the context window. See its documentation.
Servers by other publishers
5 servers for Sentry that name a public repository or a package. Anyone can publish one, and we have not read their code: check the publisher and the source before giving one a credential.
In this order: live servers before deprecated ones, first-party first, a known vulnerability last, then more downloads, then a more recent push, then by name. There is no score. Downloads are from npm and pypistats, the last push from GitHub and vulnerabilities from OSV; a server's own page has the day each was read, and "not read" means we have no figure, not that there is none. See how this directory is made.
A server is listed for Sentry when we have named it as the system's official server, when its registry title or the last part of its registry name names Sentry as whole words, or when it is published under Sentry's own domain. See how this directory is made.
Built from agent catalog version 2026-11-13.3 of , from the MCP Registry as read on . A listing here is not an endorsement: anyone can publish a server, and we have not read its code. Names, descriptions and addresses are the publisher's own. See how this directory is made, and tell us about a wrong entry through the contact page.