MCP Gateway · Cursor
Connect Exa to Cursor
Cursor users often need an answer from outside the repo: how a library is used, what a spec page says, whether an approach still works. Exa brings web search and code context into the editor's chat. Cursor hooks send each prompt and tool call to Speakeasy and fail closed, and every hook event carries the user's email, so each search is tied to a person.
- Category
- AI & search
- Tools
- 8
- Authentication
- None
- Cursor
- Editor and terminal
Behind the MCP Gateway
Run Exa MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Exa call inspected and logged.
Set up
Add Exa to Cursor in 4 steps
- 01
Add Exa from the catalog
An admin finds Exa 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 Exa
Give teams the
mcp:connectscope on the Exa server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Exa 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 Exa 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, Exa'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 Exa
Pull usage examples into the editor
Highlight a call you haven't used before and ask Cursor for examples. It finds code and documentation for that API and suggests an edit that matches the pattern.
Implement against a spec page
Paste links to an RFC, a style guide or an API reference, and Cursor reads all of them in one call as Markdown so it can write code against the actual text.
Compare libraries before adding one
Before adding a dependency, ask Cursor to search for recent comparisons and maintenance news on the candidates, then summarize the tradeoffs next to your package file.
Tools
8 tools
Each Exa tool can be allowed or denied per team and role at the MCP Gateway before Cursor sees it.
web_search_exa
Search the web for any topic and get clean, ready-to-use content.
company_research_exa
[Deprecated: Use web_search_advanced_exa instead] Research any company to get business information, news, and insights.
crawling_exa
Read a webpage's full content as clean markdown. Use after web_search_exa when highlights are insufficient or to read any URL.
people_search_exa
[Deprecated: Use web_search_advanced_exa instead] Find people and their professional profiles.
linkedin_search_exa
⚠️ DEPRECATED: This tool is deprecated. Please use 'people_search_exa' instead. This tool will be removed in a future version. For now, it searches for people on LinkedIn using Exa AI - finds professional profiles and people.
deep_researcher_start
[Deprecated] Start an AI research agent that searches, reads, and writes a detailed report. Takes 15 seconds to 2 minutes.
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 Exa call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Exa tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Exa 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 Exa usage in Cursor count toward a budget?
Can a team use Exa in Cursor without page crawling?
How do Cursor users get Exa?
Are Exa calls from Cursor logged?
Connect more