Vercel MCP connector

1. Install the SDK

   Node.js

   npm install @scalekit-sdk/node

   Python

   pip install scalekit

   Full SDK reference: Node.js | Python

2. Set your credentials

   Add your Scalekit credentials to your .env file. Find values in app.scalekit.com > Developers > API Credentials.

   .env

   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>

3. Set up the connector

   Register your Vercel MCP credentials with Scalekit so it handles the token lifecycle. You do this once per environment.

   Dashboard setup steps

   Register your Scalekit environment with the Vercel MCP connector so Scalekit handles the OAuth flow and token lifecycle for your users. Follow every step below from start to finish — by the end you will have a working connection.

   1. Create a Vercel OAuth integration

      You need a Vercel OAuth integration to get the Client ID and Client Secret that Scalekit will use to authorize your users.

      Go to the Vercel Integrations Console:

      • Open vercel.com/dashboard/integrations/console in your browser and sign in.

      • Click Create Integration (top right of the page).

      • Fill in the form:

        Field	What to enter
        Integration Name	A recognizable name, e.g. My Vercel MCP Agent
        URL Slug	Auto-generated from the name — you can leave it as-is
        Website URL	Your app’s public URL. For testing you can use https://localhost
        Short Description	Brief description of your integration

      • Leave the Redirects section empty for now. You will add the Scalekit callback URL in the next step.

      • Click Create →.

      After the integration is created, Vercel takes you to the integration’s settings page. Keep this tab open.

      Tip

      The Vercel integration is available for development immediately after creation — no marketplace publish step is required.

   2. Copy the redirect URI from Scalekit

      Scalekit gives you a callback URL that Vercel will redirect users back to after they authorize your app.

      In the Scalekit dashboard:

      • Go to app.scalekit.com and sign in.
      • In the left sidebar, click AgentKit > Connections > Create Connection.
      • Search for Vercel MCP and click Create.
      • A connection details panel opens. Find the Redirect URI field — it looks like:

        https://<YOUR_ENV>.scalekit.cloud/sso/v1/oauth/conn_<ID>/callback

      • Click the copy icon next to the Redirect URI.

   3. Add the redirect URI and copy credentials from Vercel

      Switch back to the Vercel integration tab you left open.

      Register the redirect URI:

      • In the left sidebar of your integration settings, click Credentials.
      • Scroll down to the Redirect URIs section.
      • Paste the redirect URI you copied from Scalekit into the input field.
      • Click Add URI, then click Save Changes.

      Copy your credentials:

      • Scroll up to the OAuth Credentials section.
      • Client ID — shown in plain text. Click Copy ID.
      • Client Secret — click Reveal to show the secret, then copy it.

      Caution

      The Client Secret is shown only when you click Reveal. If you lose it, you must generate a new one — this invalidates all existing connections until you update the secret in Scalekit.

   4. Configure permissions in Vercel

      • In the Vercel integration settings sidebar, click Permissions.

      • Enable the scopes your integration needs:

        Scope	Access granted
        openid	Required to issue an ID token for user identification
        email	User’s email address
        profile	User’s name, username, and profile picture
        offline_access	Refresh token for long-lived access without re-authorization

      • Click Save Changes.

   5. Add credentials in Scalekit

      Switch back to the Scalekit dashboard tab.

      • Go to AgentKit > Connections and click the Vercel MCP connection you created in step 2.

      • Fill in the credentials form:

        Field	Value
        Client ID	Paste the Client ID from step 3
        Client Secret	Paste the Client Secret from step 3
        Scopes	Enter the scopes you enabled in step 4, e.g. openid profile email offline_access

      • Click Save.

      Your Vercel MCP connection is now configured. Scalekit will use these credentials to run the OAuth flow whenever a user connects their Vercel account.

4. Authorize and make your first call

   Node.js

   quickstart.ts

   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   
   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENV_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions
   
   const connector = 'vercelmcp'
   const identifier = 'user_123'
   
   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Vercel MCP:', link)
   process.stdout.write('Press Enter after authorizing...')
   await new Promise(r => process.stdin.once('data', r))
   
   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'vercelmcp_deploytovercel',
     toolInput: {},
   })
   console.log(result)

   Python

   quickstart.py

   import os
   from scalekit.client import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()
   
   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENV_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions
   
   connection_name = "vercelmcp"
   identifier = "user_123"
   
   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Vercel MCP:", link_response.link)
   input("Press Enter after authorizing...")
   
   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="vercelmcp_deploytovercel",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)

What you can do

Connect this agent connector to let your agent:

• Webfetchvercelurl records — Fetches a Vercel deployment URL and returns the response body
• Searchverceldocumentation records — Search the Vercel documentation for information about a topic
• Replytotoolbarthread records — Add a reply message to an existing toolbar thread
• Listtoolbarthreads records — List Vercel toolbar comment threads for a team
• Listteams records — List the user’s teams
• Listprojects records — List all Vercel projects for a user (with a max of 50)

Tool list

Use the exact tool names from the Tool list below when you call execute_tool. If you’re not sure which name to use, list the tools available for the current user first.

vercelmcp_addtoolbarreaction#Add an emoji reaction to a message in a toolbar thread4 params▾

Add an emoji reaction to a message in a toolbar thread

NameTypeRequiredDescription

emojistringrequiredThe emoji character to use as the reaction (e.g. '👍', '❤️')

messageIdstringrequiredThe ID of the message to react to

teamIdstringrequiredThe ID of the team that owns the thread

threadIdstringrequiredThe ID of the toolbar thread containing the message

vercelmcp_changetoolbarthreadresolvestatus#Change the resolve status of a toolbar thread3 params▾

Change the resolve status of a toolbar thread

NameTypeRequiredDescription

resolvedbooleanrequiredSet to true to mark the thread as resolved, false to mark it as unresolved

teamIdstringrequiredThe ID of the team that owns the thread

threadIdstringrequiredThe ID of the toolbar thread to update

vercelmcp_checkdomainavailabilityandprice#Check if domain names are available for purchase and get pricing information1 param▾

Check if domain names are available for purchase and get pricing information

NameTypeRequiredDescription

namesarrayrequiredList of domain names to check for availability and pricing

vercelmcp_deploytovercel#Deploy the current project to Vercel0 params▾

Deploy the current project to Vercel

vercelmcp_edittoolbarmessage#Edit an existing message in a toolbar thread4 params▾

Edit an existing message in a toolbar thread

NameTypeRequiredDescription

markdownstringrequiredThe updated message content in Markdown format

messageIdstringrequiredThe ID of the message to edit

teamIdstringrequiredThe ID of the team that owns the thread

threadIdstringrequiredThe ID of the toolbar thread containing the message

vercelmcp_getaccesstovercelurl#Creates a temporary shareable link that bypasses authentication for a Vercel deployment URL1 param▾

Creates a temporary shareable link that bypasses authentication for a Vercel deployment URL

NameTypeRequiredDescription

urlstringrequiredThe Vercel deployment URL to create a temporary shareable access link for

vercelmcp_getdeployment#Get a specific deployment by ID or URL2 params▾

Get a specific deployment by ID or URL

NameTypeRequiredDescription

idOrUrlstringrequiredThe deployment ID or URL to retrieve

teamIdstringrequiredThe ID of the team that owns the deployment

vercelmcp_getdeploymentbuildlogs#Get the build logs of a deployment by deployment ID or URL2 params▾

Get the build logs of a deployment by deployment ID or URL

NameTypeRequiredDescription

idOrUrlstringrequiredThe deployment ID or URL whose build logs to retrieve

teamIdstringrequiredThe ID of the team that owns the deployment

vercelmcp_getproject#Get a specific project in Vercel2 params▾

Get a specific project in Vercel

NameTypeRequiredDescription

projectIdstringrequiredThe ID of the project to retrieve

teamIdstringrequiredThe ID of the team that owns the project

vercelmcp_getruntimelogs#Get runtime logs for a project or deployment4 params▾

Get runtime logs for a project or deployment

NameTypeRequiredDescription

projectIdstringrequiredThe ID of the project whose runtime logs to retrieve

teamIdstringrequiredThe ID of the team that owns the project

deploymentIdstringoptionalOptional deployment ID to filter runtime logs to a specific deployment

limitnumberoptionalMaximum number of log entries to return

vercelmcp_gettoolbarthread#Get a specific toolbar thread by ID2 params▾

Get a specific toolbar thread by ID

NameTypeRequiredDescription

teamIdstringrequiredThe ID of the team that owns the thread

threadIdstringrequiredThe ID of the toolbar thread to retrieve

vercelmcp_importclaudedesignfromurl#Import a design into Vercel from a publicly fetchable URL3 params▾

Import a design into Vercel from a publicly fetchable URL

NameTypeRequiredDescription

teamIdstringrequiredThe ID of the team to import the design into

urlstringrequiredThe publicly fetchable URL of the design to import

projectIdstringoptionalThe ID of the project to associate the design with (optional)

vercelmcp_listdeployments#List all deployments for a project4 params▾

List all deployments for a project

NameTypeRequiredDescription

projectIdstringrequiredThe ID of the project whose deployments to list

teamIdstringrequiredThe ID of the team that owns the project

limitnumberoptionalMaximum number of deployments to return

statestringoptionalFilter deployments by state (e.g. READY, ERROR, BUILDING, QUEUED, CANCELED)

vercelmcp_listprojects#List all Vercel projects for a user (with a max of 50)3 params▾

List all Vercel projects for a user (with a max of 50)

NameTypeRequiredDescription

teamIdstringrequiredThe ID of the team whose projects to list

limitnumberoptionalMaximum number of projects to return (max 50)

searchstringoptionalSearch query to filter projects by name

vercelmcp_listteams#List the user's teams0 params▾

List the user's teams

vercelmcp_listtoolbarthreads#List Vercel toolbar comment threads for a team3 params▾

List Vercel toolbar comment threads for a team

NameTypeRequiredDescription

teamIdstringrequiredThe ID of the team whose toolbar threads to list

deploymentIdstringoptionalFilter threads by deployment ID (optional)

projectIdstringoptionalFilter threads by project ID (optional)

vercelmcp_replytotoolbarthread#Add a reply message to an existing toolbar thread3 params▾

Add a reply message to an existing toolbar thread

NameTypeRequiredDescription

markdownstringrequiredThe reply message content in Markdown format

teamIdstringrequiredThe ID of the team that owns the thread

threadIdstringrequiredThe ID of the toolbar thread to reply to

vercelmcp_searchverceldocumentation#Search the Vercel documentation for information about a topic2 params▾

Search the Vercel documentation for information about a topic

NameTypeRequiredDescription

topicstringrequiredThe topic or query to search for in the Vercel documentation

limitnumberoptionalMaximum number of documentation results to return

vercelmcp_webfetchvercelurl#Fetches a Vercel deployment URL and returns the response body1 param▾

Fetches a Vercel deployment URL and returns the response body

NameTypeRequiredDescription

urlstringrequiredThe Vercel deployment URL to fetch