MCP Gateway · Cursor
Connect Sentry to Cursor
Cursor users can investigate Sentry errors from the editor where the fix will happen. The agent searches issues, counts how often an error fires and opens replays and profiles, all through the Speakeasy MCP Gateway, which logs every call against the developer who made it.
- Category
- Developer tools
- Tools
- 22
- Authentication
- OAuth
- Cursor
- Editor and terminal
Behind the MCP Gateway
Run Sentry MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Sentry call inspected and logged.
Before you start
What Sentry needs first
Any Sentry user with access to the needed organizations and projects does the Sentry side of the setup.
- You create nothing in Sentry before adding the server.
- Users can only reach what their Sentry account already can.
Set up
Add Sentry to Cursor in 4 steps
- 01
Add Sentry from the catalog
An admin finds Sentry in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
Sentry uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use Sentry
Give teams the
mcp:connectscope on the Sentry server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Sentry to their gateway on the next call, and removing it takes it away. - 03
Connect Cursor
Add the gateway to Cursor in one click from the Organization Gateway page.
On the Organization Gateway page in Speakeasy, choose Cursor under Install.
Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.
- 04
Sign in and use Sentry from Cursor
The first time Cursor connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Sentry needs its own OAuth grant, so each person connects it once. Until they do, Sentry calls fail while the rest of the gateway keeps working.
From then on, Sentry's tools appear in Cursor, limited to what the person's access allows, and every call lands in the gateway's tool logs.
For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.
Use cases
What Cursor users do with Sentry
Find what broke after a deploy
Ask Cursor which new issues appeared since the last release and how many events each one has, so you start with the error that hurts the most users.
Watch the session that failed
For a frontend bug, Cursor fetches the session replay linked to the error and summarizes what the user did before it broke, next to the component you're editing.
Chase a slow function
Pull profile data for a slow transaction and let Cursor point to the function calls that take the time, then optimize them in place.
Tools
22 tools
Each Sentry tool can be allowed or denied per team and role at the MCP Gateway before Cursor sees it.
whoami
Identify the authenticated user in Sentry.
find_organizations
Find organizations that the user has access to in Sentry.
find_teams
Find teams in an organization in Sentry.
find_projects
Find projects in Sentry.
find_releases
Find releases in Sentry.
get_issue_tag_values
Get tag value distribution for a specific Sentry issue.
Control
What Speakeasy can see and stop in Cursor
The gateway covers every client the same way. The rest depends on what Cursor exposes to Speakeasy.
Tool logs
Gateway
Every Sentry call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Sentry tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Sentry can reject a tool request before it reaches the server, or withhold a result from Cursor. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Cursor
Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.
User attribution
Cursor
Every Cursor hook event carries the user's email.
Budgets
Cursor
Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.
Device agent and MDM
Cursor
The device agent installs the marketplace and plugins and reapplies them every minute.
- Cursor Cloud agents need a checked-in
.cursor/hooks.json. Session and MCP-specific hooks don't run there. - After a plugin update, members run Developer: Reload Window.
Questions
Frequently asked questions
Can Speakeasy stop a Sentry call from Cursor before it runs?
Does this work for Cursor Cloud agents?
How do Cursor users get Sentry?
Are Sentry calls from Cursor logged?
Connect more