MCP Gateway · Cursor
Connect Vercel to Cursor
Reviewers comment on Vercel previews with the toolbar, and each thread usually points at one piece of UI. Cursor can pull that feedback into the editor while the component is open, then reply and resolve it once the fix is in. Every Vercel call goes through Speakeasy's gateway and is logged against the developer's email, and Cursor hooks check each prompt and tool call first.
- Category
- Developer tools
- Tools
- 18
- Authentication
- OAuth
- Cursor
- Editor and terminal
Behind the MCP Gateway
Run Vercel MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Vercel call inspected and logged.
Set up
Add Vercel to Cursor in 4 steps
- 01
Add Vercel from the catalog
An admin finds Vercel 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.
Vercel 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 Vercel
Give teams the
mcp:connectscope on the Vercel server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Vercel 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 Vercel from Cursor
The first time Cursor connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Vercel needs its own OAuth grant, so each person connects it once. Until they do, Vercel calls fail while the rest of the gateway keeps working.
From then on, Vercel'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 Vercel
Work through preview feedback in the editor
Ask Cursor for the team's unresolved toolbar threads, open the one about your branch, and read every message with its context beside the component it refers to.
Reply and resolve after a fix
Once the change is pushed, Cursor replies on the thread to explain what changed and marks it resolved, so the reviewer knows to look at the preview again.
Acknowledge a comment you picked up
Have Cursor react to a reviewer's message when you start on it, or correct a reply you left earlier, without switching to the browser toolbar.
Tools
18 tools
Each Vercel tool can be allowed or denied per team and role at the MCP Gateway before Cursor sees it.
search_vercel_documentation
Search the Vercel documentation.
deploy_to_vercel
Deploy the current project to Vercel
list_projects
List all Vercel projects for a user (with a max of 50). Use this to help discover the Project ID of the project that the user is working on.
get_project
Get a specific project in Vercel
list_deployments
List all deployments for a project
get_deployment
Get a specific deployment by ID or URL.
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 Vercel call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Vercel tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Vercel 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 Cursor resolve Vercel comments without access to deployments?
Do Speakeasy's Cursor hooks run in Cursor Cloud agents?
How do Cursor users get Vercel?
Are Vercel calls from Cursor logged?
Connect more