# Connect Vercel to your AI agent

> Yes — ClawLink is a hosted Vercel MCP server. 131 tools your agent can call from chat, with one-click API key and nothing to run locally.

Web version: https://claw-link.dev/hub/vercel

ClawLink hosts a managed Vercel MCP server that exposes 131 tools to your AI agent. You connect Vercel in one click, and your agent can read, create, and update Vercel data from chat without you building or running a local MCP server.

## Quick facts

- 131 tools callable from chat
- One-click API key
- Works with OpenClaw, Hermes, Claude Code, Cursor, Codex, and any MCP client
- No local server or config files

## Overview

The usual path is: build auth, handle token refresh, wire up the tools. With ClawLink you connect Vercel once and start using the real actions from the agent.

## Setup

Vercel uses an API key. You paste it once during setup and ClawLink handles the rest. No secure storage to build, no per-request auth headers to manage.

Authentication: API key

## What you can do

- **Work without tab-switching** — Pull up Vercel issues, repos, tasks, or alerts without leaving the conversation.
- **Ship the routine stuff faster** — The agent grabs Vercel context, drafts the next step, and runs the common maintenance actions.
- **Debug with real data** — Ask for the current state from Vercel before the agent suggests a fix. No guessing.

## Vercel tools

131 Vercel tools, ready the moment you connect.

- `vercel_add_environment_variable` — Add an environment variable to a Vercel project
- `vercel_add_project_domain` — Attach a domain to a Vercel project
- `vercel_create_new_deployment` — Create a new deployment in Vercel
- `vercel_create_project2` — Create a new Vercel project
- `vercel_filter_project_envs` — List environment variables for a Vercel project
- `vercel_get_auth_user` — Get the authenticated Vercel user
- `vercel_get_deployment` — Get details for a specific deployment
- `vercel_get_deployments` — List Vercel deployments
- `vercel_get_project_domains` — List domains attached to a Vercel project
- `vercel_get_project2` — Get details for a specific Vercel project
- `vercel_get_projects` — List Vercel projects
- `vercel_get_teams` — List teams accessible to the connected Vercel account
- `vercel_list_domains` — List domains in the connected Vercel account
- `vercel_update_project2` — Update project settings for a Vercel project
- `vercel_check_cache_artifact_exists` — Check if a cache artifact exists by its hash
- `vercel_check_domain_availability` — Check if a domain is available for registration
- `vercel_check_domain_price2` — Check pricing for a domain including purchase, renewal, and transfer costs
- `vercel_download_artifact` — Download a cache artifact from Vercel's Remote Cache by its hash
- `vercel_get_active_attack_status` — Read active attack data from Vercel Firewall for a specific project
- `vercel_get_alias` — Retrieve information about a Vercel alias by ID or alias name
- `vercel_get_artifact_info` — Query information about artifacts by their hashes
- `vercel_get_auth_token` — Retrieve metadata for an authentication token
- `vercel_get_bulk_availability` — Check availability for multiple domains at once
- `vercel_get_cache_status` — Get the status of Remote Caching for the principal
- `vercel_get_certs` — Retrieve SSL/TLS certificates for the authenticated user or team
- `vercel_get_configurations` — Get configurations for the authenticated user or team
- `vercel_get_contact_info_schema` — Retrieve the contact information schema for a domain's top-level domain (TLD)
- `vercel_get_deployment_events2` — Get deployment events for a specific Vercel deployment by ID or URL
- `vercel_get_deployment_file_contents` — Retrieve the contents of a specific file from a Vercel deployment
- `vercel_get_deployment_logs2` — Retrieve runtime logs for a specific Vercel deployment by project and deployment ID

## Example prompts

- **Add environment variable:** Use Vercel to add environment variable and walk me through it.
- **Add project domain:** Use Vercel to add project domain and walk me through it.
- **Create new deployment:** Create it in Vercel. Confirm the key fields with me before you finish.
- **Create project2:** Create it in Vercel. Confirm the key fields with me before you finish.

## ClawLink vs. building it yourself

| | Manual | ClawLink |
|---|---|---|
| Connection | Build it yourself. You generate and rotate Vercel API keys, store them safely, keep per-environment secrets straight, and make sure every tool call uses the right key. | Hosted API key. Connect once in the browser. ClawLink owns the lifecycle. |
| Maintenance | Token refresh, permission debugging, env config, every edge case. All yours. | ClawLink handles the plumbing. You focus on the workflow. |
| Time to first call | Days to weeks. Auth, storage, tool wiring, testing. Then the agent can act. | About two minutes from sign-up to the agent calling Vercel. |

## FAQ

### How do I connect Vercel to my AI agent?

Install ClawLink, open the dashboard, click Connect next to Vercel, and finish the API key flow. Your agent can call Vercel from the next message. Two minutes, total.

### Is there a Vercel MCP server I can use?

Yes. ClawLink exposes Vercel as 131 tools your agent calls through a hosted MCP-compatible runtime. You don't run a local server or edit a config file. The tools are there the moment you connect.

### Do I need Vercel API credentials?

Yes. You'll paste your Vercel API key once during setup. ClawLink stores it and uses it for every tool call after.

### How much does it cost?

Your first integration is free, plus a 7-day trial of the full catalog. Paid plans unlock the rest of the library.

### Can I set this up from the terminal instead of the dashboard?

Yes. Run npx -y @useclawlink/cli login, then npx -y @useclawlink/cli connect vercel. The first opens a browser to sign in to ClawLink. The second opens a browser to authorize Vercel. No API keys to create. Works with OpenClaw, Hermes, Claude Code, Cursor, Codex, and any agent that runs shell commands.