MCP Gateway · Cursor
Connect Amplitude to Cursor
When a bug report says checkout broke, Amplitude often holds the session that shows how. Through the Speakeasy MCP Gateway, the Cursor agent can replay that session's clicks and page views, read the flag that guards a code path, and open any Amplitude link pasted into a ticket. Every Cursor hook event carries the user's email, so each call is tied to a person.
- Category
- Data & analytics
- Tools
- 44
- Authentication
- OAuth
- Cursor
- Editor and terminal
Behind the MCP Gateway
Run Amplitude MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Amplitude call inspected and logged.
Before you start
What Amplitude needs first
An Amplitude organization admin does the Amplitude side of the setup.
- There is nothing to create in Amplitude. Users sign in with their own accounts and keep their existing permissions.
- US and EU organizations use different server URLs, and the two are not interchangeable.
- Custom roles need Use MCP (read) enabled, or MCP calls fail for that role.
In Amplitude
- Find your data region from the Amplitude hostname and record the matching server URL.
- In Settings, Content Access > MCP, confirm the MCP server is allowed.
- For custom roles, enable Use MCP (read), and Use MCP (write) only if needed.
Set up
Add Amplitude to Cursor in 4 steps
- 01
Add Amplitude from the catalog
An admin finds Amplitude 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.
Amplitude 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 Amplitude
Give teams the
mcp:connectscope on the Amplitude server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Amplitude 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 Amplitude from Cursor
The first time Cursor connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Amplitude needs its own OAuth grant, so each person connects it once. Until they do, Amplitude calls fail while the rest of the gateway keeps working.
From then on, Amplitude'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 Amplitude
Replay the session behind a bug
Find replays for the affected user and have Cursor read the processed timeline of page navigations, clicks and text inputs, then trace those steps through the component you have open.
Read a flag while editing
Before branching code on a feature flag, Cursor searches Amplitude for it and reads its definition, so the keys in the editor match the flag Amplitude actually serves.
Open a chart linked in a ticket
Paste an app.amplitude.com link from an issue and Cursor retrieves the chart behind it, then queries that chart so you see the same data the reporter saw.
Tools
44 tools
Each Amplitude tool can be allowed or denied per team and role at the MCP Gateway before Cursor sees it.
get_charts
Retrieve full chart objects by their IDs using the chart service directly
save_chart_edits
Save temporary chart edits as permanent charts
get_cohorts
Get detailed information about specific cohorts by their IDs.
create_cohort
Create a new cohort with the provided definition and configuration.
get_context
Get information about the current user, organization, and list of accessible projects.
get_project_context
Get project-specific settings and configuration for a specific project.
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 Amplitude call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Amplitude tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Amplitude 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
Why do Amplitude calls fail for some Cursor users?
Does Cursor pick up Amplitude plugin changes on its own?
How do Cursor users get Amplitude?
Are Amplitude calls from Cursor logged?
Connect more