MCP Gateway · Claude Code
Connect Vercel to Claude Code
When a Vercel build fails, the answer is usually in the log, and Claude Code can read it next to the code that broke. With Vercel behind the Speakeasy MCP Gateway, developers sign in through your identity provider, reach only the Vercel tools their role allows, and keep no Vercel token on the laptop. Agent hooks check each prompt and tool call before Claude Code runs it.
- Category
- Developer tools
- Tools
- 18
- Authentication
- OAuth
- Claude Code
- CLI
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 Claude Code 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 Claude Code
Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.
Run the command below with your organization gateway URL.
Open
/mcpin Claude Code and choose Authenticate to sign in.claude mcp add --transport http --scope user \ 'speakeasy' \ 'https://<organization host>/mcp/gateway/<organization slug>' - 04
Sign in and use Vercel from Claude Code
The first time Claude Code 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 Claude Code, limited to what the person's access allows, and every call lands in the gateway's tool logs.
To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.
Use cases
What Claude Code users do with Vercel
Fix a failed build from the terminal
Ask Claude Code why the latest deployment failed. It finds the deployment, reads its build log, and proposes a change to the file that caused the error.
Ship the current branch for review
Once tests pass locally, have Claude Code deploy the current project to Vercel and then look up the new deployment, so you have something concrete to share with reviewers.
Check a protected preview responds
If a preview sits behind Vercel Authentication, Claude Code can still fetch the page it serves and check the response after a change, without you opening a browser.
Tools
18 tools
Each Vercel tool can be allowed or denied per team and role at the MCP Gateway before Claude Code 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 Claude Code
The gateway covers every client the same way. The rest depends on what Claude Code 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 Claude Code. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Claude Code
Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.
User attribution
Claude Code
Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.
Budgets
Claude Code
Spend limits can block Claude Code traffic once a budget is reached.
Device agent and MDM
Claude Code
The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.
Anthropic inference hooks
Claude Code
On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).
- Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
- Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.
Questions
Frequently asked questions
Can Claude Code deploy to Vercel without a Vercel token on my machine?
Can I let Claude Code read Vercel logs but not deploy?
How do Claude Code users get Vercel?
Are Vercel calls from Claude Code logged?
Connect more