MCP Gateway · Cursor
Connect Context7 to Cursor
When Cursor suggests code for a library, the suggestion should match that library's current documentation. Context7 provides the documentation, and through the Speakeasy MCP Gateway it sits next to the other approved servers on one URL. Cursor hooks check every prompt and tool call with Speakeasy, and each hook event carries the developer's email.
- Category
- Developer tools
- Tools
- 2
- Authentication
- None
- Cursor
- Editor and terminal
Behind the MCP Gateway
Run Context7 MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Context7 call inspected and logged.
Set up
Add Context7 to Cursor in 4 steps
- 01
Add Context7 from the catalog
An admin finds Context7 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 Context7
Give teams the
mcp:connectscope on the Context7 server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Context7 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 Context7 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, Context7'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 Context7
Explain an error inside a dependency
When a stack trace points into a third-party package, Cursor finds the library in Context7 and reads its documentation for that function to explain what went wrong.
Write tests the documented way
Cursor pulls documented code examples for your testing framework and writes new tests in the style its maintainers recommend for that release.
Suggest code from current APIs
While you build a new component, Cursor queries up-to-date docs for the UI or data library it uses, so suggestions follow current APIs rather than deprecated ones.
Tools
2 tools
Each Context7 tool can be allowed or denied per team and role at the MCP Gateway before Cursor sees it.
resolve-library-id
Resolves a package/product name to a Context7-compatible library ID and returns matching libraries.
query-docs
Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework.
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 Context7 call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Context7 tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Context7 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
Is documentation returned by Context7 checked?
How do Cursor users pick up a change to the Context7 plugin?
How do Cursor users get Context7?
Are Context7 calls from Cursor logged?
Connect more