MCP Gateway · Cursor
Connect Hugging Face to Cursor
Implementing a technique from a recent paper means reading the paper, finding a reference model and checking the APIs you will call. With Hugging Face connected to Cursor through the Speakeasy MCP Gateway, the agent can do all three beside the file you are editing. Cursor hooks fail closed, so a tool call runs only once Speakeasy allows it.
- Category
- AI & search
- Tools
- 10
- Authentication
- OAuth
- Cursor
- Editor and terminal
Behind the MCP Gateway
Run Hugging Face MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Hugging Face call inspected and logged.
Set up
Add Hugging Face to Cursor in 4 steps
- 01
Add Hugging Face from the catalog
An admin finds Hugging Face 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.
Hugging Face 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 Hugging Face
Give teams the
mcp:connectscope on the Hugging Face server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Hugging Face 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 Hugging Face from Cursor
The first time Cursor connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Hugging Face needs its own OAuth grant, so each person connects it once. Until they do, Hugging Face calls fail while the rest of the gateway keeps working.
From then on, Hugging Face'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 Hugging Face
Implement from a research paper
Ask Cursor to find the paper behind a method on the Hugging Face hub, then implement the core idea in the current file with a link back to the source.
Build a Gradio demo
While you write a Gradio interface, Cursor searches the Gradio documentation and fetches the component reference you need, so the props in your code match the current release.
Test an input with a Space
Cursor discovers which Space tasks are available and runs one, such as background removal on a test image, to check what your code should expect back.
Tools
10 tools
Each Hugging Face tool can be allowed or denied per team and role at the MCP Gateway before Cursor sees it.
hf_whoami
Hugging Face tools are being used by the authenticated user
space_search
Find Hugging Face Spaces using semantic search. IMPORTANT Only MCP Servers can be used with the dynamic_space toolInclude links to the Space when presenting the results.
hub_repo_search
Search Hugging Face repositories with a shared query interface. You can target models, datasets, spaces, or aggregate across multiple repo types in one call. Use space_search for semantic-first discovery of Spaces. Include links to repositories in your response.
paper_search
Find Machine Learning research papers on the Hugging Face hub. Include 'Link to paper' When presenting the results. Consider whether tabulating results matches user intent.
hub_repo_details
Get details for one or more Hugging Face repos (model, dataset, or space). Auto-detects type unless specified.
hf_doc_search
Search and Discover Hugging Face Product and Library documentation. Send an empty query to discover structure and navigation instructions. Knowledge up-to-date as at 8 April 2026. Combine with the Product filter to focus results.
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 Hugging Face call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Hugging Face tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Hugging Face 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
Are Hugging Face tool calls in Cursor attributed to a person?
Do Hugging Face tools run in Cursor Cloud agents?
How do Cursor users get Hugging Face?
Are Hugging Face calls from Cursor logged?
Connect more