Sentry
Interact with the Sentry API to monitor application errors and performance.
Sentry MCP Server
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.
Requirements
- Node.js (v14 or higher)
- npm or yarn
- Sentry account with API access
- Sentry authentication token with appropriate permissions
Setup
- Install dependencies:
npm install
Using this within an IDE
This MCP has been verified to work against Codeium Windsurf.
Cursor is currently having issues with its MCP implementation; and this tool is not yet fully functional.
Using with Claude
To use this MCP server with Claude, add the following configuration to your Claude settings:
{
"mcpServers": {
"sentry": {
"command": "npx",
"args": ["ts-node", "/Users/<your-user-directory>/mcp-sentry-ts/index.ts"],
"env": {
"SENTRY_AUTH": "<YOUR_AUTH_TOKEN>"
}
}
}
}
- Update with your directory path in the
argsfield. - Replace
<YOUR_AUTH_TOKEN>with your Sentry authentication token.
Available Tools
list_projects
Lists all accessible Sentry projects for a given organization.
Parameters:
organization_slug(string, required): The slug of the organization to list projects fromview(string, optional): View type, either "summary" or "detailed" (default: "detailed")format(string, optional): Output format, either "plain" or "markdown" (default: "markdown")
resolve_short_id
Retrieves details about an issue using its short ID.
Parameters:
organization_slug(string, required): The slug of the organization the issue belongs toshort_id(string, required): The short ID of the issue to resolve (e.g., PROJECT-123)format(string, optional): Output format, either "plain" or "markdown" (default: "markdown")
get_sentry_event
Retrieves and analyzes a specific Sentry event from an issue.
Parameters:
issue_id_or_url(string, required): Either a full Sentry issue URL or just the numeric issue IDevent_id(string, required): The specific event ID to retrieveview(string, optional): View type, either "summary" or "detailed" (default: "detailed")format(string, optional): Output format, either "plain" or "markdown" (default: "markdown")
list_error_events_in_project
Lists error events from a specific Sentry project.
Parameters:
organization_slug(string, required): The slug of the organization the project belongs toproject_slug(string, required): The slug of the project to list events fromview(string, optional): View type, either "summary" or "detailed" (default: "detailed")format(string, optional): Output format, either "plain" or "markdown" (default: "markdown")
create_project
Creates a new project in Sentry and retrieves its client keys.
Parameters:
organization_slug(string, required): The slug of the organization to create the project inteam_slug(string, required): The slug of the team to assign the project toname(string, required): The name of the new projectplatform(string, optional): The platform for the new projectview(string, optional): View type, either "summary" or "detailed" (default: "detailed")format(string, optional): Output format, either "plain" or "markdown" (default: "markdown")
list_project_issues
Lists issues from a specific Sentry project.
Parameters:
organization_slug(string, required): The slug of the organization the project belongs toproject_slug(string, required): The slug of the project to list issues fromview(string, optional): View type, either "summary" or "detailed" (default: "detailed")format(string, optional): Output format, either "plain" or "markdown" (default: "markdown")
list_issue_events
Lists events for a specific Sentry issue.
Parameters:
organization_slug(string, required): The slug of the organization the issue belongs toissue_id(string, required): The ID of the issue to list events fromview(string, optional): View type, either "summary" or "detailed" (default: "detailed")format(string, optional): Output format, either "plain" or "markdown" (default: "markdown")
get_sentry_issue
Retrieves and analyzes a Sentry issue.
Parameters:
issue_id_or_url(string, required): Either a full Sentry issue URL or just the numeric issue IDview(string, optional): View type, either "summary" or "detailed" (default: "detailed")format(string, optional): Output format, either "plain" or "markdown" (default: "markdown")
list_organization_replays
Lists replays from a specific Sentry organization.
Parameters:
organization_slug(string, required): The slug of the organization to list replays fromproject_ids(string[], optional): List of project IDs to filter replays byenvironment(string, optional): Environment to filter replays bystats_period(string, optional): Time period for stats (e.g., "24h", "7d")start(string, optional): Start date for filtering replaysend(string, optional): End date for filtering replayssort(string, optional): Field to sort replays byquery(string, optional): Search query to filter replaysper_page(number, optional): Number of replays per pagecursor(string, optional): Cursor for paginationview(string, optional): View type, either "summary" or "detailed" (default: "detailed")format(string, optional): Output format, either "plain" or "markdown" (default: "markdown")
Running the Server
npx ts-node index.ts
Authentication
This tool requires a Sentry authentication token with appropriate permissions to access the Sentry API. You can generate a token in your Sentry account settings under "API Keys".
Error Handling
The server includes comprehensive error handling for:
- Missing authentication token
- API request failures
- Invalid parameters
- Network errors
All errors are logged to the console for debugging.
関連サーバー
Alpha Vantage MCP Server
スポンサーAccess financial market data: realtime & historical stock, ETF, options, forex, crypto, commodities, fundamentals, technical indicators, & more
DevRev MCP Server
Access DevRev's APIs to manage work items, parts, search, and user information.
BCMS MCP
Give me a one - two sentence description of the BCMS MCP # MCP The BCMS Model Context Protocol (MCP) integration enables AI assistants like Claude, Cursor, and other MCP-compatible tools to interact directly with your BCMS content. This allows you to create, read, and update content entries, manage media files, and explore your content structure—all through natural language conversations with AI. ## What is MCP? The [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) is an open standard developed by Anthropic that allows AI applications to securely connect to external data sources and tools. With BCMS MCP support, you can leverage AI assistants to: - Query and explore your content structure - Create new content entries with AI-generated content - Update existing entries - Manage your media library - Get intelligent suggestions based on your content model --- ## Getting Started ### Prerequisites 1. A BCMS account with an active instance 2. An MCP key with appropriate permissions 3. An MCP-compatible client (Claude Desktop, Cursor, or any MCP client) ### Step 1: Create an MCP Key 1. Navigate to your BCMS dashboard 2. Go to Settings → MCP 3. Click Create MCP Key 4. Configure the permissions for templates you want the AI to access:GET: Read entries 5. POST: Create entries 6. PUT: Update entries 7. DELETE: Delete entries Note: Right now, MCP only supports creating, reading and updating content. ### Step 2: Configure Your MCP Client You can find full instructions for integrating BCMS with your AI tools right inside BCMS, on the MCP page. But in general, installing BCMS MCP works in a standard way: ``` { "mcpServers": { "bcms": { "url": "https://app.thebcms.com/api/v3/mcp?mcpKey=YOUR_MCP_KEY" } } } ``` ## Available Tools Once connected, your AI assistant will have access to the following tools based on your MCP key permissions: ### Content Discovery #### list_templates_and_entries Lists all templates and their entries that you have access to. This is typically the first tool to call when exploring your BCMS content. Returns: - Template IDs, names, and slugs - Entry IDs with titles and slugs for each language Example prompt: "Show me all the templates and entries in my BCMS" --- ### Entry Management #### list_entries_for_{templateId} Retrieves all entries for a specific template with full content data. A separate tool is generated for each template you have access to. Returns: - Complete entry data including all meta fields - Content in all configured languages - Entry statuses Example prompt: "List all blog posts from my Blog template" --- #### create_entry_for_{templateId} Creates a new entry for a specific template. The input schema is dynamically generated based on your template's field structure. Input: - statuses: Array of status assignments per language - meta: Array of metadata for each language (title, slug, custom fields) - content: Array of content nodes for each language Example prompt: "Create a new blog post titled 'Getting Started with BCMS' with a brief introduction paragraph" --- #### update_entry_for_{templateId} Updates an existing entry for a specific language. Input: - entryId: The ID of the entry to update - lng: Language code (e.g., "en") - status: Optional status ID - meta: Updated metadata - content: Updated content nodes Example prompt: "Update the introduction paragraph of my 'Getting Started' blog post" --- ### Media Management #### list_all_media Lists all media files in your media library. Returns: - Media IDs, names, and types - File metadata (size, dimensions for images) - Parent directory information Example prompt: "Show me all images in my media library" --- #### list_media_dirs Lists the directory structure of your media library. Returns: - Hierarchical directory structure - Directory IDs and names Example prompt: "Show me the folder structure of my media library" --- #### create-media-directory Creates a new directory in your media library. Input: - name: Name of the directory - parentId: Optional parent directory ID (root if not specified) Example prompt: "Create a new folder called 'Blog Images' in my media library" --- #### request-upload-media-url Returns a URL you use to upload a file (for example via POST with multipart form data), which avoids pushing large binaries through the MCP tool payload. You still need a valid file name and MIME type when uploading, as described in the tool response. Availability: Only when the MCP key has Can mutate media enabled. Example prompt: “Give me an upload URL for a new hero image, then tell me how to upload it.” Input: - fileName: Name of the file with extension - fileData: Base64-encoded file data (with data URI prefix) - parentId: Optional parent directory ID Example prompt: "Upload this image to my Blog Images folder" --- ### Linking Tools #### get_entry_pointer_link Generates an internal BCMS link to an entry for use in content. Input: - entryId: The ID of the entry to link to Returns: - Internal link format: entry:{entryId}@*_{templateId}:entry Example prompt: "Get me the internal link for the 'About Us' page entry" --- #### get_media_pointer_link Generates an internal BCMS link to a media item for use in content. Input: - mediaId: The ID of the media item Returns: - Internal link format: media:{mediaId}@*_@*_:entry Example prompt: "Get the link for the hero image so I can use it in my blog post" --- ## Content Structure ### Entry Content Nodes When creating or updating entries, content is structured as an array of nodes. Supported node types include: Type Description paragraph Standard text paragraph heading Heading (h1-h6) bulletList Unordered list orderedList Numbered list listItem List item codeBlock Code block with syntax highlighting blockquote Quote block image Image node widget Custom widget with props ### Example Content Structure ``` { "content": [ { "lng": "en", "nodes": [ { "type": "heading", "attrs": { "level": 1 }, "content": [ { "type": "text", "text": "Welcome to BCMS" } ] }, { "type": "paragraph", "content": [ { "type": "text", "text": "This is your first paragraph." } ] } ] } ] } ``` ## Security & Permissions ### MCP Key Scopes Your MCP key controls what the AI can access: - Template Access: Only templates explicitly granted in the MCP key are visible - Operation Permissions: Each template can have independent GET/POST/PUT/DELETE permissions - Media Access: Media operations are controlled separately ### Best Practices 1. Principle of Least Privilege: Only grant the permissions needed for your use case 2. Separate Keys: Create different MCP keys for different purposes or team members 3. Regular Rotation: Periodically rotate your MCP keys ## Use Cases ### Content Creation Workflows Blog Post Creation "Create a new blog post about the benefits of headless CMS. Include an introduction, three main benefits with explanations, and a conclusion. Use the Blog template." Product Updates "Update the price field for all products in the Electronics category to apply a 10% discount" ### Content Exploration Content Audit "List all blog posts that don't have a featured image set" Translation Status "Show me which entries are missing German translations" ### Media Organization Library Cleanup "Show me all unused images in the media library" Folder Setup "Create folder structure for: Products > Categories > Electronics, Clothing, Home" ## Troubleshooting ### Common Issues #### "MCP key not found" - Verify your MCP key format: keyId.keySecret.instanceId - Ensure the MCP key hasn't been deleted or deactivated - Check that you're using the correct instance #### "MCP key does not have access to template" - Review your MCP key permissions in the dashboard - Ensure the required operation (GET/POST/PUT/DELETE) is enabled for the template #### Session Expired - MCP sessions may timeout after periods of inactivity - Simply start a new conversation to establish a fresh session ### Getting Help - Documentation: [thebcms.com/docs](https://thebcms.com/docs) - Support: [[email protected]](mailto:[email protected]) - Community: [Join BCMS Discord](https://discord.com/invite/SYBY89ccaR) for community support ## Technical Reference ### Endpoint POST https://app.thebcms.com/api/v3/mcp?mcpKey={MCP_KEY} ### Transport BCMS MCP uses the Streamable HTTP transport with session management. Sessions are maintained via the mcp-session-id header. ### Response Format All tools return structured JSON responses conforming to the MCP specification with: - content: Array of content blocks - structuredContent: Typed response data ## Rate Limits MCP requests are subject to the same rate limits as API requests: - Requests are tracked per MCP key - Contact support if you need higher limits for production workloads
React Native AI Debugger
Enables AI assistants like Claude Code to capture logs, execute code, inspect state, and control navigation in your React Native app.
Composer Package README MCP Server
Fetches comprehensive information about Composer packages from Packagist, including READMEs, metadata, and search functionality.
PsiAnimator-MCP
A server for quantum physics simulation and animation, using QuTip for computations and Manim for visualizations.
Kubernetes
Kubernetes MCP server with the top30 tools
Google MCP Servers
Collection of Google's official MCP servers
jarp-mcp
Java Archive Reader Protocol MCP server - Give AI agents X-ray vision into compiled Java code by decompiling JAR/WAR/EAR files and Maven/Gradle dependencies
Last9
Seamlessly bring real-time production context—logs, metrics, and traces—into your local environment to auto-fix code faster.
i18next MCP Server
An MCP server for managing translations in i18next projects, allowing AI assistants to interact directly with translation files.