sentry-selfhosted-mcp

Created By
ddfourtwoa year ago
An MCP server for self-hosted sentry.
Overview

What is Sentry Self-Hosted MCP?

Sentry Self-Hosted MCP is a Model Context Protocol server designed for interacting with self-hosted Sentry instances, allowing users to manage and retrieve information about issues within their Sentry setup.

How to use Sentry Self-Hosted MCP?

To use the server, clone the repository, install the dependencies, and configure the necessary environment variables for your Sentry instance. Then, run the server to interact with your Sentry projects and issues.

Key features of Sentry Self-Hosted MCP?

  • Retrieve details for specific Sentry issues by ID or URL.
  • List all projects within a configured Sentry organization.
  • Filter and list issues for specific projects based on query or status.
  • Update the status of Sentry issues.
  • Add comments to Sentry issues.

Use cases of Sentry Self-Hosted MCP?

  1. Managing and tracking issues in self-hosted Sentry instances.
  2. Automating the retrieval of issue details for reporting.
  3. Facilitating team collaboration by commenting on issues directly.

FAQ from Sentry Self-Hosted MCP?

  • What is required to run the server?

You need to set environment variables for SENTRY_URL, SENTRY_AUTH_TOKEN, and SENTRY_ORG_SLUG to connect to your Sentry instance.

  • Is there a specific programming language used?

Yes, the server is built using JavaScript and requires Node.js for execution.

  • Can I customize the server's functionality?

Yes, you can modify the source code to add or change features as per your requirements.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ddfourtwo
Star
0
Language
JavaScript
License
MIT license
Category
monitoring

Recommend Servers

View All
Alloy

2 days 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)

8 hours ago
Crevio

a day ago