mcp-error-tracer: An MCP gateway for Sentry integration

Synopsis

A Model Context Protocol (MCP) endpoint designed for fetching and interpreting data residing within Sentry.io. This utility furnishes mechanisms to probe exception manifests, stack traces, and associated debugging metadata linked to your Sentry tenancy.

Available Utilities

1. fetch_sentry_record
2. Gathers and processes a specific Sentry incident identified via its unique identifier or endpoint URL.
3. Parameters:
   • issue_id_or_url (text): The unique identifier or full URL pointing to the Sentry anomaly.
4. Output Schema (Incident Manifest):
   • Designation (Title)
   • Incident Identifier
   • Operational State (Status)
   • Severity Rating (Level)
   • Initial Observation Time
   • Most Recent Observation Time
   • Event Tally
   • Complete Execution Traceback (Stacktrace)
5. list_project_incidents
6. Retrieves and analyzes a collection of Sentry incidents scoped by a designated project identifier.
7. Parameters:
   • project_slug (text): The unique key identifying the Sentry project.
   • organization_slug (text): The unique key identifying the Sentry organization.
8. Output Schema (Incident Summary List):
   • Designation
   • Incident Identifier
   • Operational State
   • Severity Rating
   • Initial Observation Time
   • Most Recent Observation Time
   • Event Tally
   • Essential incident metadata

Operational Prompts

1. sentry-context-retriever
2. Obtains detailed context regarding a fault report from the Sentry service.
3. Parameters:
   • issue_id_or_url (text): The identifier or locator for the Sentry incident.
4. Output: A structured representation of the incident details formatted for conversational context injection.

Deployment Procedures

Integration via Smithery

To automatically incorporate mcp-error-tracer for use with Claude Desktop via Smithery:

bash npx -y @smithery/cli install @qianniuspace/mcp-sentry --client claude

Execution with uv (Preferred)

When employing uv for dependency management, explicit setup is circumvented. We leverage uvx to invoke mcp-error-tracer directly.

Conventional PIP Installation

Alternatively, the package can be installed using pip:

pip install mcp-sentry

or utilizing uv:

uv pip install -e .

Post-installation, execution can be initiated via the module entry point:

python -m mcp_sentry

Configuration Schema

Integration with Claude Desktop

Inject the following structure into your claude_desktop_config.json file:

Using uvx Executor

"mcpServers": { "sentry": { "command": "uvx", "args": ["mcp-sentry", "--auth-token", "YOUR_SENTRY_TOKEN","--project-slug" ,"YOUR_PROJECT_SLUG", "--organization-slug","YOUR_ORGANIZATION_SLUG"] } }

Using Docker Container

"mcpServers": { "sentry": { "command": "docker", "args": ["run", "-i", "--rm", "mcp/sentry", "--auth-token", "YOUR_SENTRY_TOKEN","--project-slug" ,"YOUR_PROJECT_SLUG", "--organization-slug","YOUR_ORGANIZATION_SLUG"] } }

Using Locally Installed PIP Package

"mcpServers": { "sentry": { "command": "python", "args": ["-m", "mcp_sentry", "--auth-token", "YOUR_SENTRY_TOKEN","--project-slug" ,"YOUR_PROJECT_SLUG", "--organization-slug","YOUR_ORGANIZATION_SLUG"] } }

Integration with Zed

Amend your Zed configuration file (settings.json) as follows:

Using uvx Executor in Zed

For Example Cursor Positioning "context_servers": [ "mcp-sentry": { "command": { "path": "uvx", "args": ["mcp-sentry", "--auth-token", "YOUR_SENTRY_TOKEN","--project-slug" ,"YOUR_PROJECT_SLUG", "--organization-slug","YOUR_ORGANIZATION_SLUG"] } } ],

Using Locally Installed PIP Package in Zed

"context_servers": { "mcp-sentry": { "command": "python", "args": ["-m", "mcp_sentry", "--auth-token", "YOUR_SENTRY_TOKEN","--project-slug" ,"YOUR_PROJECT_SLUG", "--organization-slug","YOUR_ORGANIZATION_SLUG"] } },

Using PIP Installation with Custom Module Path in Zed

"context_servers": { "sentry": { "command": "python", "args": [ "-m", "mcp_sentry", "--auth-token", "YOUR_SENTRY_TOKEN", "--project-slug", "YOUR_PROJECT_SLUG", "--organization-slug", "YOUR_ORGANIZATION_SLUG" ], "env": { "PYTHONPATH": "path/to/mcp-sentry/src" } } },

Diagnostics

Debugging operations can be performed utilizing the MCP inspector utility. For setups managed by uvx:

npx @modelcontextprotocol/inspector uvx mcp-sentry --auth-token YOUR_SENTRY_TOKEN --project-slug YOUR_PROJECT_SLUG --organization-slug YOUR_ORGANIZATION_SLUG

If the package resides in a specific development location:

cd path/to/servers/src/sentry npx @modelcontextprotocol/inspector uv run mcp-sentry --auth-token YOUR_SENTRY_TOKEN --project-slug YOUR_PROJECT_SLUG --organization-slug YOUR_ORGANIZATION_SLUG

or in a terminal session:

npx @modelcontextprotocol/inspector uv --directory /Volumes/ExtremeSSD/MCP/mcp-sentry/src run mcp_sentry --auth-token YOUR_SENTRY_TOKEN --project-slug YOUR_PROJECT_SLUG --organization-slug YOUR_ORGANIZATION_SLUG

Derivation From

• https://github.com/modelcontextprotocol/servers/tree/main/src/sentr

Licensing

This MCP server is distributed under the MIT License terms. Permission is granted to utilize, adapt, and disseminate this software, contingent upon adherence to the specified conditions of the MIT License. Full documentation is available in the repository's LICENSE file.

WIKIPEDIA: Web development tools (often abbreviated to dev tools) allow web developers to test, modify and debug their websites. They are different from website builders and integrated development environments (IDEs) in that they do not assist in the direct creation of a webpage, rather they are tools used for testing the user interface of a website or web application. Web development tools come as browser add-ons or built-in features in modern web browsers. Browsers such as Google Chrome, Firefox, Safari, Microsoft Edge, and Opera have built-in tools to help web developers, and many additional add-ons can be found in their respective plugin download centers. Web development tools allow developers to work with a variety of web technologies, including HTML, CSS, the DOM, JavaScript, and other components that are handled by the web browser.

== Genealogy and Assistance == Early web developers manually debugged their websites by commenting out code and using JavaScript functions. One of the first browser debugging tools to exist was Mozilla's Firebug extension, which possessed many of the current core features of today's developer tools, leading to Firefox becoming popular with developers at the time. Safari's WebKit engine also introduced its integrated developer tools around that period, which eventually became the basis for both Safari and Chrome's current tooling. Microsoft released a developer toolbar for Internet Explorer 6 and 7; and then integrated them into the browser from version 8 onwards. In 2017, Mozilla discontinued Firebug in favour of integrated developer tools. Nowadays, all modern web browsers have support for web developer tools that allow web designers and developers to look at the make-up of their pages. These are all tools that are built into the browser and do not require additional modules or configuration.

Firefox – F12 opens the Firefox DevTools. Google Chrome and Opera – Developer Tools (DevTools) Microsoft Edge – F12 opens Web Developer Tools. Microsoft incorporates additional features that are not included in mainline Chromium. Safari – The Safari Web Inspector has to be enabled from its settings pane.

== Capabilities == The built-in web developer tools in the browser are commonly accessed by hovering over an item on a webpage and selecting the "Inspect Element" or similar option from the context menu. Alternatively the F12 key tends to be another common shortcut.

=== HTML and the DOM === HTML and DOM viewer and editor is commonly included in the built-in web development tools. The difference between the HTML and DOM viewer, and the view source feature in web browsers is that the HTML and DOM viewer allows you to see the DOM as it was rendered in addition to allowing you to make changes to the HTML and DOM and see the change reflected in the page after the change is made. In addition to selecting and editing, the HTML elements panels will usually also display properties of the DOM object, such as display dimension, and CSS