Skip to main content
Back to the Vercel MCP server

MCP Gateway · Claude Cowork

Vercel icon

Connect Vercel to Claude Cowork

Launch prep for a new site spans several checks: picking a domain, confirming the build, reviewing the page and clearing feedback. In Cowork, Claude can work through that list as one longer task against Vercel. The server reaches Cowork through the organization's synced plugin, and Speakeasy's agent hooks send each prompt to be allowed or denied before the step runs.

Category
Developer tools
Tools
18
Authentication
OAuth
Claude Cowork
Cowork tab in Claude Desktop

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 Cowork 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. Claude Cowork connects to the Vercel server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect Claude Cowork

    Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.

    New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.

    Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.

    In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.

    Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.

    In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.

  4. 04

    Sign in and use Vercel from Claude Cowork

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

Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.

Use cases

What Claude Cowork users do with Vercel

Shortlist domains for a new site

Give Cowork a set of name ideas. It checks which domains are available to buy, notes the price of each, and returns a ranked shortlist for the team to choose from.

check_domain_availability_and_price

Review a site before launch

Cowork reads the project's settings, fetches the protected preview page by page, and writes up anything that looks broken or missing in a launch checklist.

get_projectweb_fetch_vercel_url

Clear a backlog of review threads

Cowork goes through every unresolved toolbar thread, replies with the status of each item, and resolves the ones that are already handled.

list_toolbar_threadsreply_to_toolbar_threadchange_toolbar_thread_resolve_status

Tools

18 tools

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

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

Prompt blocking

Claude Cowork

Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.

Session telemetry

Claude Cowork

Cowork's OTLP export ties sessions to people and feeds observability.

Anthropic inference hooks

Claude Cowork

On Claude Enterprise, prompts can be checked before inference (beta).

  • Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
  • Personal Claude accounts can't be governed in Cowork.

Questions

Frequently asked questions

Do Cowork members need GitHub access to get the Vercel plugin?
No. Cowork reads the synced plugin repository, so a new session picks up changes, and members who receive plugins through Cowork don't need a GitHub invitation.
Can personal Claude accounts use Vercel through Cowork?
Personal Claude accounts can't be governed in Cowork. Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
How do Claude Cowork users get Vercel?
An admin adds Vercel from the Speakeasy MCP Catalog and grants access by team or role. Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork. Each person then sees only the Vercel tools their access allows.
Are Vercel calls from Claude Cowork 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.