
MCP Server Sentry
A TypeScript implementation of a Model Context Protocol server that connects to Sentry error tracking service, allowing AI models to query and analyze error reports and events.
README
MCP Server Sentry - TypeScript Implementation
This is a Model Context Protocol (MCP) server implemented in TypeScript for connecting to the Sentry error tracking service. This server allows AI models to query and analyze error reports and events on Sentry.
Features
-
get_sentry_issue
Tool- Retrieves and analyzes Sentry issues by ID or URL
- Input:
issue_id_or_url
(string): Sentry issue ID or URL to analyze
- Returns: Issue details including:
- Title
- Issue ID
- Status
- Level
- First seen timestamp
- Last seen timestamp
- Event count
- Complete stack trace
-
sentry-issue
Prompt Template- Retrieves issue details from Sentry
- Input:
issue_id_or_url
(string): Sentry issue ID or URL
- Returns: Formatted issue details as conversation context
Installation
# Install dependencies
npm install
# Build the project
npm run build
Configuration
The server is configured using environment variables. Create a .env
file in the project root directory:
# Required: Sentry authentication token
SENTRY_AUTH_TOKEN=your_sentry_auth_token
# Optional: Sentry organization name
SENTRY_ORGANIZATION_SLUG=your_organization_slug
# Optional: Sentry project name
SENTRY_PROJECT_SLUG=your_project_slug
# Optional: Sentry base url
SENTRY_BASE_URL=https://sentry.com/api/0
Alternatively, you can set these environment variables at runtime.
Running
Run the server via standard IO:
node dist/index.js
Debug with MCP Inspector:
npx @modelcontextprotocol/inspector node dist/index.js
Environment Variables Description
SENTRY_AUTH_TOKEN
(required): Your Sentry API access tokenSENTRY_PROJECT_SLUG
(optional): The slug of your Sentry projectSENTRY_ORGANIZATION_SLUG
(optional): The slug of your Sentry organization
The latter two variables can be omitted if project and organization information are provided in the URL.
License
This project is licensed under the MIT License.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.