Skip to main content
Back to the Cube MCP server

MCP Gateway · Cursor

Cube icon

Connect Cube to Cursor

Reports, charts and internal tools are only as right as the analytics data under them. From the editor, Cursor can explore that data through Cube and have SQL generated from a plain description, without a separate BI login. Speakeasy's Cursor hooks fail closed, and every hook event records the developer's email.

Category
Data & analytics
Authentication
None
Cursor
Editor and terminal

Behind the MCP Gateway

Run Cube MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Cube call inspected and logged.

Deploy on MCP Gateway

Set up

Add Cube to Cursor in 4 steps

  1. 01

    Add Cube from the catalog

    An admin finds Cube 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.

    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.

  2. 02

    Choose who can use Cube

    Give teams the mcp:connect scope on the Cube server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Cube to their gateway on the next call, and removing it takes it away.

  3. 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.

  4. 04

    Sign in and use Cube from Cursor

    The first time Cursor connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    From then on, Cube'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 Cube

Write a report query beside the handler

Building an internal report endpoint? Ask Cursor to have Cube generate the SQL for the figure you need, then use it in the handler you're editing.

Debug an odd value in a chart

When a chart in your app shows a surprising value, Cursor explores the same analytics data through Cube to see whether the problem is in the data or the component.

Look at real values before modeling

Before adding a field to an API response or type, explore the analytics data in Cube from Cursor to see which values actually occur.

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 Cube call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Cube tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Cube 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

Do Cursor Cloud agents run Speakeasy's hooks for Cube?
Only partly. Cursor Cloud agents need a checked-in .cursor/hooks.json, and session and MCP-specific hooks don't run there.
Can budgets cover Cursor sessions that query Cube?
Spend limits can block Cursor traffic once a budget is reached. For dollar spend, connect the Cursor Admin API.
How do Cursor users get Cube?
An admin adds Cube from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway to Cursor in one click from the Organization Gateway page. Each person then sees only the Cube tools their access allows.
Are Cube calls from Cursor logged?
Yes. Cube calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Cube in other clients

AI everywhere.

Control here.