Skip to main content
Back to the Vercel MCP server

MCP Gateway · OpenCode

Vercel icon

Connect Vercel to OpenCode

OpenCode users can follow a Vercel deployment from the same terminal session that pushed it, from build output through to function errors. The server is added as a remote entry in OpenCode's mcp config, and Speakeasy's gateway decides which Vercel tools each role can call. The OpenCode plugin sends every prompt and tool call to Speakeasy, which allows or denies it before it runs.

Category
Developer tools
Tools
18
Authentication
OAuth
OpenCode
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.

Deploy on MCP Gateway

Set up

Add Vercel to OpenCode 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. OpenCode 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 OpenCode

    Add the server to OpenCode's own mcp config block as a remote server.

    Copy the server's URL from its hosted install page in Speakeasy.

    Add it to the mcp block of your OpenCode config with type set to remote.

    Restart OpenCode and sign in when prompted.

    {
      "mcp": {
        "<server slug>": {
          "type": "remote",
          "url": "<URL from the hosted install page>"
        }
      }
    }
  4. 04

    Sign in and use Vercel from OpenCode

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

OpenCode doesn't receive MCP servers from plugins. The observability package is installed separately, from a ZIP or with speakeasy-hooks install --provider=opencode, and the device agent can maintain it.

Use cases

What OpenCode users do with Vercel

Stream a build while it runs

After a push, ask OpenCode to follow the build logs for the new deployment as they arrive, and stop as soon as an error shows up so you can fix it.

get_deployment_build_logs

Confirm what is live

OpenCode lists a project's deployments and reads the details of the newest one, so you know which commit is serving traffic before you start debugging.

list_deploymentsget_deployment

Search function output after a deploy

Run a full-text search over runtime logs for an error message or status code from a single deployment, and have OpenCode point to the handler that wrote it.

get_runtime_logs

Tools

18 tools

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

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

Prompt and tool-call blocking

OpenCode

The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it before it runs.

Usage telemetry

OpenCode

Token and cost totals flow through the plugin, reported per turn.

Device agent

OpenCode

The device agent installs and maintains the observability package.

  • OpenCode has no OpenTelemetry exporter, so session data comes through the plugin.
  • Tool output is blocked at the gateway rather than in OpenCode's hooks.

Questions

Frequently asked questions

How does OpenCode report usage for Vercel sessions?
OpenCode has no OpenTelemetry exporter, so session data comes through the Speakeasy plugin, which reports token and cost totals per turn.
Where is Vercel tool output blocked for OpenCode?
At the gateway rather than in OpenCode's hooks. Prompt injection detection and PII redaction run on every Vercel tool call there, and each call is logged against a named employee.
How do OpenCode users get Vercel?
An admin adds Vercel from the Speakeasy MCP Catalog and grants access by team or role. Add the server to OpenCode's own mcp config block as a remote server. Each person then sees only the Vercel tools their access allows.
Are Vercel calls from OpenCode 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.