Sentry MCP setup: find errors in the right project

An error report is useful only when it belongs to the intended application and time range. Prepare a known issue URL from a test project before making your first request. Record the project, environment and a timestamp. This guide proposes a read test for your environment; no authenticated test with your Sentry account was performed here.

Choose the organisation and project first

Sentry documents the remote endpoint https://mcp.sentry.dev/mcp with OAuth sign-in. You can extend the address with an organisation slug and then a project slug. Use the actual identifiers from your Sentry environment. This selection sets the context for tools; still verify account permissions and the project named in the response.

A complete VS Code example

{
  "servers": {
    "sentry": {
      "type": "http",
      "url": "https://mcp.sentry.dev/mcp"
    }
  }
}

Add this configuration to the intended workspace. In an existing file, add only the entry inside servers. For a project selection, replace the URL with https://mcp.sentry.dev/mcp/ORGANISATION/PROJECT; the uppercase words are placeholders. Start the connection and complete sign-in in your browser. The VS Code guide explains the file structure. Do not add an access token to the example URL.

Use one known issue as a read test

1. Open the known issue yourself first. Record its identifier and one non-sensitive property you can recognise in the later response.

2. Inspect the available tools. Choose a read operation for that exact issue and explicitly constrain the time range if you search.

3. Compare the returned project, issue identifier and time range against the browser view. A similar error title is not enough to identify an issue.

4. Request the same information again after restarting the client. Record whether authentication and the project context survive the restart.

Diagnose empty responses one step at a time

Check the project, environment and time filter separately when a response is empty. Do not change the account and query at the same time: doing so makes the cause harder to identify later. A visible tool list does not establish access to the intended issue. The troubleshooting navigator helps isolate connection errors, while the permission planner records intended access.

The provider repository documents a separate route for self-hosted deployments. Review its prerequisites independently of cloud sign-in. A successful read test does not establish that writes, other projects or every function work. Find other implementations through the registry search, or use the app guide directory to explore related operations tools.

Common Sentry MCP questions

Which URL should I start with?

The documented cloud endpoint is https://mcp.sentry.dev/mcp. You can append organisation and project slugs.

Why is a known issue missing?

Compare the account, project, environment and time range with the Sentry interface. Check each value separately.

Does project scoping mean read-only?

No. Context selection and allowed operations are separate questions. Inspect the offered tools and account permissions.

Can I connect a self-hosted instance the same way?

Do not assume the cloud endpoint applies. The provider repository describes a separate deployment route.

Provider sources checked on 2 October 2026. The checks are proposals for your own environment.

1. Sentry MCP
   Show retrieval command

   curl -s https://mcp.sentry.dev/
2. Sentry repository
   Show retrieval command

   curl -s https://github.com/getsentry/toolkit

All posts