Vercel

Developer tools

Vercel for AI agents. Managed auth, ready-made tools.

Check deployments, read build logs, manage environment variables and redeploy in your users' Vercel projects.

About Vercel

With the Vercel connector, your agent checks on each user’s own Vercel projects through Agent200: it lists deployments, reads build logs when one fails, manages environment variables and redeploys. Every user connects their own account through managed OAuth.

Vercel is a cloud platform for building and deploying web applications, with a preview deployment for every change and production deployments from Git.

Tools

What your agent can do in Vercel.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Vercel connection.

  • List projects

    Read
    vercel_list_projects

    List the projects in the connected account or team.

  • List deployments

    Read
    vercel_list_deployments

    List recent deployments with their state and target.

  • Get a deployment

    Read
    vercel_get_deployment

    Read a deployment's status, URL and Git source.

  • Get build logs

    Read
    vercel_get_deployment_events

    Read the build output of a deployment.

  • List environment variables

    Read
    vercel_list_env_vars

    List a project's environment variables and their targets.

  • Add an environment variable

    Write
    vercel_create_env_var

    Add an environment variable to a project.

  • Redeploy

    Write
    vercel_create_deployment

    Create a new deployment from an existing one.

Control

Limits you can set.

You decide what your agent may do in Vercel, and Agent200 runs every call within those limits.

  • Turn single tools on or off

    Let your agent read deployments and logs, and switch off vercel_create_deployment and vercel_create_env_var if it should never change a project.

  • Restrict what the agent reaches

    Choose the endpoints and scopes a project may use. A call outside them is refused.

Get started

Connect Vercel
in three steps.

  1. 1

    Set up the SDK

    Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 2

    Let your user connect Vercel

    Each end user authorizes their own Vercel account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // Each end user authorizes their own Vercel account, once.
    const connection = await agent200
      .user("user_123")
      .connect("vercel");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  3. 3

    Run with the Vercel tools

    Name the user, the model and the tools. The model decides which Vercel tools to call, and Agent200 executes them with that user's connection.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "Why did the last production deployment fail",
        tools: ["vercel"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, on Vercel's own page. You never see or store their Vercel credentials.

  • What access is requested

    The user picks the account or team to connect, and Vercel shows the permissions requested, such as reading deployments and managing environment variables.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Vercel connector and how to use it.

Agent brief
Connector: Vercel, through Agent200. In code: "vercel".
What it does: Check deployments, read build logs, manage environment variables and redeploy in your users' Vercel projects.
Page: https://www.agent200.com/tools/vercel/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Vercel's own page, through the authorization link Agent200 returns. Never ask a user for a Vercel password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: vercel_list_projects, vercel_list_deployments, vercel_get_deployment, vercel_get_deployment_events, vercel_list_env_vars. Write tools: vercel_create_env_var, vercel_create_deployment. Name "vercel" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/tools/vercel/framework/claude/
   https://www.agent200.com/tools/vercel/framework/chatgpt/
   https://www.agent200.com/tools/vercel/framework/claude-code/
   https://www.agent200.com/tools/vercel/framework/muse/
   https://www.agent200.com/tools/vercel/framework/grok-bot/
   https://www.agent200.com/tools/vercel/framework/openai-dots/
   https://www.agent200.com/tools/vercel/framework/claude-duet/
   https://www.agent200.com/tools/vercel/framework/hermes-agent/
   https://www.agent200.com/tools/vercel/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

This page is also available as Markdown, for agents and LLMs: /tools/vercel.md

Guides

Use Vercel with the AI you build on.

Step-by-step setup for Vercel with a specific model, assistant or agent framework.

FAQ

Vercel and Agent200, answered.

Who handles the Vercel OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Vercel.

Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Vercel connection, never another user's. It cannot reach anything the user or Vercel has not authorized.

Can I limit what my agent can do in Vercel?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

  • GitHub

    GitHub

    Read repositories and work with issues and pull requests as the connected user.

    Managed OAuth Developer tools
  • GitLab

    GitLab

    Review merge requests, file issues, read code and check pipelines in your users' GitLab projects.

    Managed OAuth Developer tools
  • Bitbucket

    Bitbucket

    List and open pull requests, comment, read code and check pipelines in your users' Bitbucket workspaces.

    Managed OAuth Developer tools
  • Jira

    Jira

    Search, create and transition Jira issues for the connected user.

    Managed OAuth Developer tools
200 OK

Start with Vercel.
Your agent does the rest.

Your users connect their own Vercel accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)