Sentry Mcp

Created By
Zzzccs1235 months ago
Overview

what is Sentry Mcp?

Sentry Mcp is a Model Context Protocol (MCP) server implemented in TypeScript that connects to the Sentry error tracking service, allowing AI models to query and analyze error reports and events.

how to use Sentry Mcp?

To use Sentry Mcp, install the dependencies, configure the required environment variables, and run the server using Node.js. You can also debug it with the MCP Inspector.

key features of Sentry Mcp?

  • get_sentry_issue Tool: Retrieves and analyzes Sentry issues by ID or URL, providing detailed information about the issue.
  • sentry-issue Prompt Template: Formats issue details from Sentry for conversation context.

use cases of Sentry Mcp?

  1. Analyzing error reports from Sentry for AI model training.
  2. Integrating Sentry error tracking with AI applications.
  3. Automating the retrieval of issue details for debugging purposes.

FAQ from Sentry Mcp?

  • What is required to run Sentry Mcp?

You need a Sentry authentication token and Node.js installed on your machine.

  • Can I customize the configuration?

Yes! You can set environment variables for Sentry organization and project names, as well as the base URL.

  • Is Sentry Mcp open source?

Yes! This project is licensed under the MIT License.

Server Config

{
  "mcpServers": {
    "sentry-mcp": {
      "command": "node",
      "args": [
        "mcp-server/sentry/dist/index.js"
      ]
    }
  }
}
Project Info
Created At
5 months ago
Updated At
5 months ago
Author Name
Zzzccs123
Star
-
Language
-
License
-

Recommend Servers

View All
Crevio

a day ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

19 hours ago