Sentry Sensei

You can connect your Sentry and JIRA workflows to an MCP server that exposes a set of operations you can request from an LLM or automation client. This server fetches Sentry data like organizations, projects, and issues, and retrieves JIRA ticket details, enabling seamless cross-tool queries and updates through a remote or local MCP setup.

How to use

Use a compatible MCP client to connect to the Sentry Sensei MCP server. You can run the server either remotely (via a hosted MCP endpoint) or locally (on your machine) and configure your client to send requests for Sentry and JIRA data. Typical usage includes listing organizations, listing projects, fetching issues, and retrieving detailed JIRA ticket information. You can invoke the available tools through natural language prompts or structured requests supported by your MCP client.

How to install

{
  "mcpServers": {
    "sentry_sensei_http": {
      "type": "http",
      "url": "https://sentry-sensei-mcp.netlify.app/mcp",
      "name": "sentry_sensei_http",
      "args": []
    },
    "sentry_sensei_dev": {
      "type": "stdio",
      "name": "sentry_sensei_dev",
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "http://localhost:3000//mcp",
        "--header",
        "X-Sentry-Host:${SENTRY_HOST}",
        "--header",
        "X-Sentry-Organization:${SENTRY_ORG}",
        "--header",
        "X-Sentry-Token:${SENTRY_TOKEN}",
        "--header",
        "X-Atlassian-Domain:${ATLASSIAN_DOMAIN}",
        "--header",
        "X-Jira-Token:${JIRA_TOKEN}",
        "--header",
        "X-Jira-Email:${JIRA_EMAIL}"
      ],
      "env": {
        "SENTRY_HOST": "https://your-org.sentry.io",
        "SENTRY_ORG": "your-org-slug",
        "SENTRY_TOKEN": "your-sentry-token",
        "ATLASSIAN_DOMAIN": "your-company.atlassian.net",
        "JIRA_TOKEN": "your-jira-api-token",
        "JIRA_EMAIL": "your-email@company.com"
      }
    }
  }
}

Additional configuration and running tips

Prerequisites you need on your machine: Node.js installed and npm available. You will run commands from your terminal to install dependencies, start the development server, or connect to the remote MCP endpoint.

Steps to run locally (development mode):

npm install
npm run dev

Security and credentials handling

Pass credentials securely through HTTP headers as shown in the configuration examples. Avoid hardcoding tokens in shared files. Use environment variables or secret management where possible, and only expose endpoints to trusted clients.

Notes on usage with LPCMs and clients

The MCP endpoint supports both remote (http) and local (stdio) configurations. When using a local runtime, the command includes the package invocation (such as npx) and passes headers as part of the arguments. Ensure your client is configured to forward the required headers for SENTRY_HOST, SENTRY_ORG, SENTRY_TOKEN, ATLASSIAN_DOMAIN, JIRA_TOKEN, and JIRA_EMAIL.

Available tools

get_sentry_organizations

List all Sentry organizations you have access to.

get_sentry_projects

List projects for a given Sentry organization.

get_sentry_issues

Fetch Sentry issues with support for environment, date range, and other filters.

get_sentry_issue_details

Retrieve detailed information for a specific Sentry issue.

get_jira_issue_details

Get detailed information for a specific JIRA ticket.

get_jira_fields

Retrieve available fields for JIRA tickets (useful for updates).

edit_jira_issue

Update fields on a JIRA ticket.