Model Context Protocol (MCP) server for Sentry
Model Context Protocol (MCP) server for Sentry
A Model Context Protocol (MCP) server for interacting with Sentry. This MCP server provides tools to interact with the Sentry API, allowing AI assistants to retrieve and analyze error data, manage projects, and monitor application performance.
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| list_projects | Lists all accessible Sentry projects for a given organization. |
| resolve_short_id | |
| get_sentry_event | Retrieves and analyzes a specific Sentry event from an issue. |
| list_error_events_in_project | |
| create_project | Creates a new project in Sentry and retrieves its client keys. |
| list_project_issues | |
| list_issue_events | |
| get_sentry_issue | |
| list_organization_replays |
| Variable | Description | Required |
|---|---|---|
| SENTRY_AUTH | Configuration value read at startup. | Optional |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
LiveNX Network Observability MCP Server
Install and launch dockit and/or sqlkit, add a database connection, and make sure Settings → MCP Bridge → Auto-start is enabled (it is by default). Install both apps for the full SQL + NoSQL tool set.
Query and analyze your Opik logs, traces, prompts and all other telemtry data from your LLMs in natural language.
MCP server for Paessler PRTG's REST API v2 - network/infrastructure monitoring for MSPs.