MCP Gateway · Cursor
Connect Glean to Cursor
Cursor knows your repository, but not the wiki pages, specs and threads around it. Glean fills that gap: the editor's chat can search company knowledge while the code stays open. If Speakeasy can't be reached, Cursor's hooks fail closed, and because each event includes the developer's email, every search is attributed.
- Category
- Productivity
- Authentication
- None
- Cursor
- Editor and terminal
Behind the MCP Gateway
Run Glean MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Glean call inspected and logged.
Set up
Add Glean to Cursor in 4 steps
- 01
Add Glean from the catalog
An admin finds Glean 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.
- 02
Choose who can use Glean
Give teams the
mcp:connectscope on the Glean server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Glean 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 Glean 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, Glean'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 Glean
Read the spec next to the code
Ask Cursor to find the product spec for the feature you're building in Glean, then check your implementation against the requirements it lists.
Find the owner of a component
When you're about to change shared code, Cursor searches Glean for the team or person who owns it, so you know whom to tag on the pull request.
Explain an internal acronym
Hit a variable or comment that uses an internal term you don't know? Ask Cursor to look it up in Glean and explain it in context.
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 Glean call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Glean tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Glean 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
What do Cursor users do after the Glean plugin changes?
Do Glean controls apply to Cursor Cloud agents?
How do Cursor users get Glean?
Are Glean calls from Cursor logged?
Connect more