How to Use the Vercel MCP in Claude Code

Q: How do I automate Vercel deployments with Claude Code?

You script the process by calling createverceldeployment. The terminal executes this command, triggering a build, and you can follow up by using getverceldeploymentinfo to check the exit code.

Q: Can Claude Code manage Vercel environment variables for CI/CD?

Yes. You use addvercelenvironmentvariable and listvercelprojectenvvars within your shell script. This guarantees that the correct secrets are available when the build runs.

Q: How do I list Vercel projects using Claude Code?

Simply execute listvercelprojects. The output provides a machine-readable list of every project name you need to target in your scripts.

Q: Is the MCP Server useful for managing Vercel account domains with Claude Code?

Yes. You run listvercelaccountdomains to get a definitive, scriptable list of all custom domains associated with the target Vercel account.

Automate Vercel deployments and manage infrastructure using Claude Code in a headless terminal environment.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Vercel MCP to Claude Code

Create your Vinkius account to connect Vercel to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Vercel with Claude Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Automating the full deployment lifecycle via MCP Server

Run build pipelines end-to-end from the command line. You can trigger new releases with `create_vercel_deployment` or verify the status of a job using `get_vercel_deployment_info`. This is perfect for CI/CD hooks. Need to tear down old staging environments? Call `delete_vercel_deployment` in your script, or list all recent builds using `list_vercel_deployments`.

Auditing Vercel project and user credentials

Scripts need context. The MCP Server lets you gather necessary info by calling `get_vercel_user_profile` to confirm permissions, or listing all projects with `list_vercel_projects`. You can also check which teams are accessible using `list_vercel_teams`. Understanding the full scope is easy: run `list_vercel_account_domains`.

Managing environment variables in automated workflows

When running a cron job, you can't rely on manual input. The tools allow your script to list current secrets using `list_vercel_project_env_vars`, or programmatically inject new values via `add_vercel_environment_variable`. This makes configuration reliable. If you need general app details for a log entry, use `get_vercel_project_details`.

Setup guide

Set up Vercel MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see vercel-extended-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Vercel transactions." It will automatically discover and invoke the available Vercel tools.

Terminal

claude mcp add --transport http vercel-extended-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Vercel MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

{
  "mcpServers": {
    "vercel-extended-mcp": {
      "type": "url",
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Vercel. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Vercel now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Vercel MCP in Claude Code

You script the process by calling `create_vercel_deployment`. The terminal executes this command, triggering a build, and you can follow up by using `get_vercel_deployment_info` to check the exit code.

Yes. You use `add_vercel_environment_variable` and `list_vercel_project_env_vars` within your shell script. This guarantees that the correct secrets are available when the build runs.

Simply execute `list_vercel_projects`. The output provides a machine-readable list of every project name you need to target in your scripts.

Yes. You run `list_vercel_account_domains` to get a definitive, scriptable list of all custom domains associated with the target Vercel account.

It touches infrastructure and configuration details, specifically the Project Environment Variables. This is essential for backend scripts that need to access secrets or settings.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript