Connect Vercel to Claude Code

Inspect projects, deployments, domains, and build logs. Add Toolspoke to Claude Code once and it can use 11 Vercel actions. Your Vercel credential stays in Toolspoke, and you choose which actions Claude Code may call.

Set it up in Claude Code

Three steps, the first one once for every toolkit you will ever add.

  1. Add Toolspoke to Claude Code

    Run it in your project, then /mcp to sign in

    claude mcp add --transport http toolspoke https://toolspoke.com/mcp

    The sign-in opens in your browser, and Toolspoke asks you to approve it.

  2. Install Vercel and connect it

    Add Vercel to a project in your Toolspoke workspace.

    Access token. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

    Access token
    Vercel dashboard → Account Settings → Tokens. Scope the token to the team you want this tool to reach.
  3. Choose what Claude Code may do

    All 11 actions start on. Switch off any of the 2 actions that change something in Vercel, and Claude Code gets a refusal if it tries.

What you can ask Claude Code for

A few of the Vercel actions that only read, so they are safe to try first.

  • List projects for the account or team, with each project's latest deployment
  • List deployments newest first, optionally scoped to one project, environment, branch, or state
  • Retrieve one deployment by id or hostname: state, target, aliases, commit metadata, and any error code
  • Return the build log lines for a deployment, newest first by default

What Claude Code can do in Vercel

9 actions read and 2 write.

Reads

  • List projects

    List projects for the account or team, with each project's latest deployment. Start here when you need a project id or name.

  • Get project

    Retrieve one project's full settings by id or name: framework, build and install commands, root directory, regions, and protection settings. Environment variables are omitted, use list_env_vars for those.

  • List deployments

    List deployments newest first, optionally scoped to one project, environment, branch, or state. Use to find the deployment that is live, or the one that failed.

  • Get deployment

    Retrieve one deployment by id or hostname: state, target, aliases, commit metadata, and any error code. Call deployment_logs for the build output itself.

  • Deployment logs

    Return the build log lines for a deployment, newest first by default. This is a different endpoint from get_deployment, use it to find out why a build failed.

  • List project domains

    List the domains attached to a project, including verification state and any redirect target.

  • List env vars

    List a project's environment variables: key, target environments, type, and comment. Values are never returned, use this to check which variables exist and where they apply.

  • List teams

    List the teams this token can reach, with their ids and slugs. Call this when you need a team_id for the other actions.

  • Whoami

    Return the account that owns this token: id, username, email, and default team. Use to confirm which account the credential reaches.

Writes

  • Add project domain

    Attach a domain to a project, optionally as a redirect or pinned to a Git branch. Returns verified:false plus a DNS challenge when the domain still needs verification. Remove a domain from the Vercel dashboard, this tool does not delete domains.

  • Upsert env var

    Create an environment variable on a project, or overwrite its value if the key already exists for the same targets. The new value only reaches the site after the next deployment.

Vercel in Claude Code: questions

Does Claude Code see my Vercel credential?

No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.

Can I stop Claude Code from changing things in Vercel?

Yes. Each of the 11 actions can be switched off for a project. Turn off the 2 that change something and Claude Code can only read.

Will 11 actions crowd Claude Code's context?

No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the Vercel action it needs when it needs it. Adding more toolkits does not add more tools to its list.

Can I add it once for every project?

Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.

What does it cost?

Tool calls are free on every plan, and a Vercel call does not run in a sandbox, so it bills nothing.

Try Vercel in Claude Code

Free to start, and tool calls cost nothing on any plan.