Skip to main content
Back to the Vercel MCP server

MCP Gateway · Claude

Vercel icon

Connect Vercel to Claude

Designers, marketers and account managers often need something from Vercel without opening the dashboard: a link to a preview, a plan detail, a list of sites. Added as a custom connector, the Speakeasy gateway lets them ask Claude directly, and each person only sees the Vercel tools their role can reach. No one needs a client ID, a secret or a Vercel credential.

Category
Developer tools
Tools
18
Authentication
OAuth
Claude
Web, desktop and mobile

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.

Deploy on MCP Gateway

Set up

Add Vercel to Claude in 4 steps

  1. 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.

  2. 02

    Choose who can use Vercel

    Give teams the mcp:connect scope 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.

  3. 03

    Connect Claude

    Add the gateway URL as a custom connector, then connect it from Customize > Connectors.

    On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.

    Each person opens Customize > Connectors and clicks Connect to sign in.

    On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.

  4. 04

    Sign in and use Vercel from Claude

    The first time Claude 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, limited to what the person's access allows, and every call lands in the gateway's tool logs.

No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.

Use cases

What Claude users do with Vercel

Share a protected preview with a client

Ask Claude for a temporary link to a preview that sits behind Vercel Authentication. The link works without a login and expires after 23 hours.

get_access_to_vercel_url

Answer a plan or billing question

Ask Claude how Vercel plans, spend management or billing work, and get an answer drawn from a search of the Vercel documentation rather than from memory.

search_vercel_documentation

See which sites your team runs

Get a list of the Vercel teams you belong to and the projects under each, which helps when a stakeholder asks where a microsite or landing page is hosted.

list_teamslist_projects

Tools

18 tools

Each Vercel tool can be allowed or denied per team and role at the MCP Gateway before Claude 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.

See all 18 tools

Control

What Speakeasy can see and stop in Claude

The gateway covers every client the same way. The rest depends on what Claude 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. MCP-scoped policies are enabled per organization.

Anthropic inference hooks

Claude

On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.

Conversation import

Claude

Claude conversations can be imported through Anthropic's Compliance API for review after the fact.

  • Custom connectors need a Claude plan that supports them.
  • Budgets don't cover Claude web and desktop usage.

Questions

Frequently asked questions

Can Claude prompts that use Vercel be blocked?
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Do Speakeasy budgets apply to Vercel use in Claude?
No. Budgets don't cover Claude web and desktop usage. Vercel tool calls are still logged at the gateway against the person who made them.
How do Claude users get Vercel?
An admin adds Vercel from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway URL as a custom connector, then connect it from Customize > Connectors. Each person then sees only the Vercel tools their access allows.
Are Vercel calls from Claude logged?
Yes. Vercel calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Vercel in other clients

AI everywhere.

Control here.