Vercel

Live

API KEY

DEPLOYMENT

Developer Tools

Every deployment, project, and domain your engineering team ships lives in Vercel. Vercel MCP gives your agent authenticated access to deployment infrastructure scoped to the user who authorized it.

  • Acts as the user: Access and write actions stay tied to the Vercel account that authorized the agent.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: Permissions enforced. 90-day audit trail.
Vercel
agent · Acme Q3
Run
Which deployments failed in the last 24 hours and what errors did they produce?
S
vercel_deployments_list
54ms
DevOps agent
3 failed deployments in the last 24 hours. api-gateway: build error — missing env var REDIS_URL (2h ago). dashboard: module not found ./components/Chart (5h ago). auth-service: out of memory at build step (9h ago). All 3 on main branch.
Sources: Vercel, failed builds, last 24h
vercelmcp
3 deployments
18:29
Message Claude...

Tools your devops agent reaches for on Vercel, scoped per user.

CALL ANY TOOL
List and inspect deployments, retrieve build logs, browse projects, and check domain status.
vercel_deployments_list
List deployments
List Vercel deployments with project and state filters.
Parameters
Name
Type
Required
Description
project_id
string
Optional
Filter by project ID
state
string
Optional
Filter: READY, ERROR, CANCELED, BUILDING, QUEUED
limit
integer
Optional
Max deployments
vercel_deployment_get
Get deployment
vercel_projects_list
List projects
vercel_domains_list
List domains
vercel_logs_get
Get build logs
Build your Agent
Drop the toolkit in, point it at the user, and your devops agent can use Vercel from the first run.
import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["vercel"], toolNames: ["vercel_deployments_list", "vercel_deployment_get", "vercel_projects_list"] },
pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
name: t.tool.definition.name,
description: t.tool.definition.description,
schema: z.object({}).passthrough(),
func: async (args) => {
const { data } = await sk.tools.executeTool({
toolName: t.tool.definition.name,
identifier: "user_123",
params: args,
});
return JSON.stringify(data);
},
}));

const agent = createReactAgent({ llm, tools: lcTools });
import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["vercel"], toolNames: ["vercel_deployments_list", "vercel_deployment_get", "vercel_projects_list"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
type: "function",
function: {
name: t.tool.definition.name,
description: t.tool.definition.description,
parameters: t.tool.definition.input_schema,
},
}));

const resp = await openai.responses.create({
model: "gpt-4o", input: prompt, tools: llmTools,
});
import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["vercel"], toolNames: ["vercel_deployments_list", "vercel_deployment_get", "vercel_projects_list"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
name: t.tool.definition.name,
description: t.tool.definition.description,
input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
model: "claude-sonnet-4-6", max_tokens: 1024,
tools: llmTools,
messages: [{ role: "user", content: prompt }],
});
import { Agent } from "@google/adk/agents";
import {
MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
connectionParams: new StreamableHTTPConnectionParams({
url: "https://mcp.scalekit.com/vercel",
headers: { Authorization: `Bearer ${userScopedToken}` },
}),
});

const agent = new Agent({
name: "agent", model: "gemini-2.0-flash",
tools: await toolset.getTools(),
});
Try these prompts
Paste any prompt into your agent to start using Vercel.
Deployments
Copy the prompt
Copied
List all failed deployments today.
Copy the prompt
Copied
Get build logs for deployment [id].
Copy the prompt
Copied
Which deployments are currently building?
Copy the prompt
Copied
Get details for the latest production deployment of [project].
Projects & domains
Copy the prompt
Copied
List all Vercel projects.
Copy the prompt
Copied
Which projects deployed in the last hour?
Copy the prompt
Copied
List all custom domains.
Copy the prompt
Copied
Which domains have SSL issues?
Debugging
Copy the prompt
Copied
Get error logs for failed deployment [id].
Copy the prompt
Copied
Why did [project] deployment fail?
Copy the prompt
Copied
List deployments with build errors this week.
Copy the prompt
Copied
Get runtime logs for [deployment id].
SEE HOW AUTH WORKS
Users authorize Vercel once. Their credentials stay vaulted, every call is checked, and every action is logged.
1
Authorize
Your user connects
Vercel
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Vercel
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Vercel
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Vercel
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
Same per-user auth pattern across other devops agents and MCP connectors. Working code, live demos, fork what fits.
ENGINEERING
DevOps assistant agent
Triage GitHub incidents, open Linear tickets, and notify the on-call channel in Slack with context already attached.
ENGINEERING
Auto-release notes agent
Group merged GitHub PRs by feature, fix, or chore and publish release notes per tag. No manual changelog grooming.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.
// shared token
 audit → bot_service_account
 user_filter → broken

 // scalekit
 audit → user_abc
 scope → enforced ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Vercel today. Others tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access Vercel as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.
Where is the Vercel api key stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.
Can I limit what the agent is allowed to do in Vercel?
Yes. Pass a tool name filter to listScopedTools so the DevOps agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Vercel.
What happens when a user revokes Vercel access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.
Can the agent trigger a new deployment or rollback?
Read and inspect operations work out of the box. Triggering deployments or rollbacks requires the API key to have the appropriate Vercel team permissions. Scope the key to read-only if write access is not needed.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""vercel"": {
""url"": ""https://mcp.scalekit.com/vercel"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.vercel]
url = ""https://mcp.scalekit.com/vercel""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""vercel"": {
""url"": ""https://mcp.scalekit.com/vercel"",
""type"": ""http""
}
}
}