メニュー
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.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/build-with-dhiraj/ai-workflow-framework-portability-kit --skill vercel-apiコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
AI image generation for SEO assets: OG/social preview images, blog hero images, schema images, product photography, infographics. Powered by Gemini via nanobanana-mcp. Requires banana extension installed. Use when user says "generate image", "OG image", "social preview", "hero image", "blog image", "product photo", "infographic", "seo image", "create visual", "image-gen", "favicon", "schema image", "pinterest pin", "generate visual", "banner", or "thumbnail".
Live SEO data via DataForSEO MCP server. SERP analysis (Google, Bing, Yahoo, YouTube, Google Images), keyword research (volume, difficulty, intent, trends), backlink profiles, on-page analysis (Lighthouse, content parsing), competitor analysis, content analysis, business listings, AI visibility (ChatGPT scraper, LLM mention tracking), and domain analytics. Requires DataForSEO extension installed. Use when user says "dataforseo", "live SERP", "keyword volume", "backlink data", "competitor data", "AI visibility check", "LLM mentions", "image SERP", "google images", "image rankings", or "real search data".
Full-site crawling, scraping, and site mapping via Firecrawl MCP. Use when user says "crawl site", "map site", "full crawl", "find all pages", "broken links", "site structure", "discover pages", "JS rendering", or needs site-wide analysis.
SOC 職業分類に基づく
SKILL.md を表示中
| name | vercel-api |
| description | 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. |
| metadata | {"priority":7,"docs":["https://vercel.com/docs/rest-api"],"sitemap":"https://vercel.com/sitemap/docs.xml","pathPatterns":[".mcp.json",".vercel/project.json"],"bashPatterns":["\\bnpm\\s+(install|i|add)\\s+[^\\n]*@vercel/sdk\\b","\\bpnpm\\s+(install|i|add)\\s+[^\\n]*@vercel/sdk\\b","\\bbun\\s+(install|i|add)\\s+[^\\n]*@vercel/sdk\\b","\\byarn\\s+add\\s+[^\\n]*@vercel/sdk\\b","\\bclaude\\s+mcp\\s+add\\b[^\\n]*\\bvercel\\b","\\bmcp\\.vercel\\.com\\b"]} |
| retrieval | {"aliases":["vercel rest api","vercel mcp","platform api","vercel sdk"],"intents":["call vercel api","use mcp server","manage deployments via api","query vercel data"],"entities":["MCP","REST API","vercel api","deployments","domains"]} |
| chainTo | [{"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."}] |
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.
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.
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.
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 |
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
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
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
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
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.
When the MCP server doesn't cover a use case (or for write operations), use the Vercel REST API directly with @vercel/sdk or curl.
# Bearer token auth (personal token or team token)
curl -H "Authorization: Bearer $VERCEL_TOKEN" https://api.vercel.com/v9/projects
// @vercel/sdk
import { Vercel } from '@vercel/sdk';
const vercel = new Vercel({ bearerToken: process.env.VERCEL_TOKEN });
| Endpoint | Method | Purpose |
|---|---|---|
/v9/projects | GET | List all projects |
/v9/projects/:id | GET | Get project details |
/v13/deployments | GET | List deployments |
/v13/deployments | POST | Create a deployment |
/v13/deployments/:id | GET | Get deployment details |
/v9/projects/:id/env | GET | List environment variables |
/v9/projects/:id/env | POST | Create environment variable |
/v6/domains | GET | List domains |
/v6/domains | POST | Add a domain |
/v1/edge-config | GET | List Edge Configs |
/v1/firewall | GET | List firewall rules |
/v1/drains | GET | List all drains |
/v1/drains | POST | Create a drain |
/v1/drains/:id/test | POST | Test a drain |
/v1/drains/:id | PATCH | Update a drain |
/v1/drains/:id | DELETE | Delete a drain |
/v3/deployments/:id/events | GET | Stream runtime logs |
import { Vercel } from '@vercel/sdk';
const vercel = new Vercel({ bearerToken: process.env.VERCEL_TOKEN });
const { deployments } = await vercel.deployments.list({
projectId: 'prj_xxxxx',
limit: 10,
});
for (const d of deployments) {
console.log(`${d.url} — ${d.state} — ${d.created}`);
}
// List env vars
const { envs } = await vercel.projects.getProjectEnv({
idOrName: 'my-project',
});
// Create env var
await vercel.projects.createProjectEnv({
idOrName: 'my-project',
requestBody: {
key: 'DATABASE_URL',
value: 'postgres://...',
target: ['production', 'preview'],
type: 'encrypted',
},
});
const { domains } = await vercel.projects.getProjectDomains({
idOrName: 'my-project',
});
for (const d of domains) {
console.log(`${d.name} — verified: ${d.verified}`);
}
/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.
import { Vercel } from '@vercel/sdk';
const vercel = new Vercel({ bearerToken: process.env.VERCEL_TOKEN });
// List all drains
const drains = await vercel.logDrains.getLogDrains({ teamId: 'team_xxxxx' });
// Create a drain
await vercel.logDrains.createLogDrain({
teamId: 'team_xxxxx',
requestBody: {
url: 'https://your-endpoint.example.com/logs',
type: 'json',
sources: ['lambda', 'edge', 'static'],
environments: ['production'],
},
});
For payload schemas (JSON, NDJSON), signature verification, and vendor integration setup, see
⤳ skill: observability.
/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 = await fetch(
`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.
| 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 |
⤳ skill: vercel-cli⤳ skill: vercel-functions⤳ skill: vercel-storage⤳ skill: vercel-firewall⤳ skill: ai-sdk (section: MCP Integration)⤳ skill: observability