Vercel MCP and REST API expert guidance. Use when the agent needs live access to Vercel projects, deployments, environment variables, domains, logs, or documentation through the MCP server or REST API.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Vercel MCP and REST API expert guidance. Use when the agent needs live access to Vercel projects, deployments, environment variables, domains, logs, or documentation through the MCP server or REST API.
[{"pattern":"vercel\\.deployments\\.(create|list)|vercel\\.projects\\.(create|update)","targetSkill":"deployments-cicd","message":"Vercel SDK deployment/project operations detected — loading CI/CD guidance for deployment workflows, preview URLs, and promotion strategies."},{"pattern":"mcp\\.vercel\\.com|claude\\s+mcp\\s+add.*vercel","targetSkill":"ai-sdk","message":"Vercel MCP server configuration detected — loading AI SDK guidance for MCP client integration and tool calling patterns."}]
Vercel API — MCP Server & REST API
You are an expert in the Vercel platform APIs. This plugin bundles a connection to the official Vercel MCP server (https://mcp.vercel.com) which gives agents live, authenticated access to Vercel resources.
MCP Server (Public Beta)
The plugin's .mcp.json configures the official Vercel MCP server using Streamable HTTP transport with OAuth authentication. The MCP server is in public beta — read-only in the initial release. Write operations are on the roadmap. Supported clients: Claude, Cursor, and VS Code.
Connection
URL: https://mcp.vercel.com
Transport: Streamable HTTP
Auth: OAuth 2.1 (automatic — agent is prompted to authorize on first use)
On first connection the agent will open a browser-based OAuth flow to grant read access to your Vercel account. Subsequent sessions reuse the stored token.
Available MCP Tools
The Vercel MCP server exposes these tool categories (read-only in initial release):
Category
Capabilities
Documentation
Search and navigate Vercel docs, Next.js docs, AI SDK docs
Projects
List projects, get project details, view project settings
Deployments
List deployments, inspect deployment details, view build output
Logs
Query deployment logs, function invocation logs, build logs
Domains
List domains, check domain configuration and DNS status
Environment Variables
List env vars per project and environment
Teams
List teams, view team members and settings
Usage Patterns
Diagnose a failed deployment
1. List recent deployments → find the failed one
2. Inspect deployment → get error summary
3. Query build logs → identify root cause
4. Cross-reference with vercel-functions skill for runtime fixes
Audit project configuration
1. Get project details → check framework, build settings, root directory
2. List environment variables → verify required vars are set per environment
3. List domains → confirm production domain is correctly assigned
4. Check deployment logs → look for runtime warnings
Search documentation
1. Search Vercel docs for a topic → get relevant pages
2. Read specific doc page → extract configuration examples
3. Cross-reference with bundled skills for deeper guidance
Debug function performance
1. Query function logs → find slow invocations
2. Inspect deployment → check function region, runtime, memory
3. Cross-reference with vercel-functions skill for optimization patterns
Deploying Your Own MCP Server
Use the mcp-handler package (renamed from @vercel/mcp-adapter) to build and deploy custom MCP servers on Vercel with Next.js, Nuxt, or SvelteKit:
npm install mcp-handler
MCP servers deployed on Vercel use Streamable HTTP transport (replaced SSE in March 2025 MCP spec) — cuts CPU usage vs SSE with no persistent connections required. Used in production by Zapier, Composio, Vapi, and Solana.
const { domains } = await vercel.projects.getProjectDomains({
idOrName: 'my-project',
});
for (const d of domains) {
console.log(`${d.name} — verified: ${d.verified}`);
}
Observability APIs
Drains (/v1/drains)
Drains forward logs, traces, speed insights, and web analytics data to external endpoints. All drain management is REST API or Dashboard (https://vercel.com/dashboard/{team}/~/settings/log-drains) only — no CLI commands exist.
For payload schemas (JSON, NDJSON), signature verification, and vendor integration setup, see ⤳ skill: observability.
Runtime Logs (/v3/deployments/:id/events)
Stream runtime logs for a deployment. The response uses application/stream+json — each line is a separate JSON object. Always set a timeout to avoid hanging on long-lived streams.
// Query via MCP (recommended for agents)// Use the get_runtime_logs MCP tool for structured log access// Direct REST alternative (streaming)const res = awaitfetch(
`https://api.vercel.com/v3/deployments/${deploymentId}/events`,
{ headers: { Authorization: `Bearer ${process.env.VERCEL_TOKEN}` } }
);
// Parse as NDJSON — see observability skill for streaming code patterns
vercel api CLI Command (January 2026)
The vercel api command gives agents direct access to the full Vercel REST API from the terminal with no additional configuration. It uses the CLI's existing authentication, so agents like Claude Code can call any endpoint immediately.
# Call any REST endpoint directly
vercel api GET /v9/projects
vercel api GET /v13/deployments
vercel api POST /v9/projects/:id/env --body '{"key":"MY_VAR","value":"val","target":["production"]}'
This bridges the gap between the read-only MCP server and the full REST API — agents can perform write operations without needing @vercel/sdk or manual curl with tokens.
When to Use MCP vs CLI vs REST API
Scenario
Use
Why
Agent needs to inspect/read Vercel state
MCP server
OAuth, structured tools, no token management
Agent needs to deploy or mutate state
CLI (vercel deploy, vercel env add)
Full write access, well-tested
Agent needs ad-hoc API access
vercel api
Direct REST from terminal, no token setup
Programmatic access from app code
REST API / @vercel/sdk
TypeScript types, fine-grained control
CI/CD pipeline automation
CLI + VERCEL_TOKEN
Scriptable, --prebuilt for speed
Searching Vercel documentation
MCP server
Indexed docs, AI-optimized results
Cross-References
CLI operations → ⤳ skill: vercel-cli
Function configuration → ⤳ skill: vercel-functions
