Vercel Deploy
Deploy websites to Vercel and return the live URL.
How to use
You have these MCP tools available:
mcp__vercel__vercel_deploy — Deploy files to Vercel. Returns the deployment URL.mcp__vercel__vercel_list_projects — List existing projects.mcp__vercel__vercel_list_deployments — List recent deployments.mcp__vercel__vercel_get_deployment — Get deployment details.mcp__vercel__vercel_create_project — Create a new project.mcp__vercel__vercel_delete_project — Delete a project.
Workflow
When the user asks you to create and deploy a website:
- Build the content in memory — Compose HTML/CSS/JS as strings. Do NOT write files to disk first.
- Deploy directly — Pass the strings straight to
mcp__vercel__vercel_deploy:
name: project name (lowercase, hyphens only)files: array of {file: "path", data: "content"} objects — data is the raw file content as a stringprojectSettings: only set when using a known framework (see below). For plain HTML/CSS/JS sites, do NOT pass projectSettings at all.
- Return the URL — The deploy tool returns a URL. Share it with the user.
Important: Do NOT write files to disk and then read them back to pass to the deploy tool. This causes unnecessary read/escape loops. Build the content and pass it directly to data.
Example
For a simple static site:
mcp__vercel__vercel_deploy({
name: "my-site",
files: [
{ file: "index.html", data: "<html>...</html>" },
{ file: "style.css", data: "body { ... }" }
]
})
Critical: projectSettings.framework rules
The Vercel API will reject the deploy with a 400 error if projectSettings.framework is not an exact match from the allowed list. To avoid this:
- Plain HTML/CSS/JS sites → Do NOT include
projectSettings at all. Omit it entirely. Vercel auto-detects static sites.
- Known frameworks only → Only set
framework if the project actually uses one of these: nextjs, vite, astro, remix, svelte, sveltekit, nuxtjs, gatsby, vue, angular, create-react-app, solidstart, hugo, jekyll, eleventy, redwoodjs.
- When in doubt → Omit
projectSettings. It is always safer to let Vercel auto-detect than to guess a framework value.
Notes
- Each deploy creates a unique URL. The latest deploy is also available at
<project-name>.vercel.app.
- If VERCEL_API_TOKEN is not set, all tools will fail with an error.
1---2name: vercel-deploy3description: Deploy websites to Vercel using MCP tools. Use when the user asks to deploy, publish, or host a website.4---56# Vercel Deploy78Deploy websites to Vercel and return the live URL.910## How to use1112You have these MCP tools available:1314- `mcp__vercel__vercel_deploy` — Deploy files to Vercel. Returns the deployment URL.15- `mcp__vercel__vercel_list_projects` — List existing projects.16- `mcp__vercel__vercel_list_deployments` — List recent deployments.17- `mcp__vercel__vercel_get_deployment` — Get deployment details.18- `mcp__vercel__vercel_create_project` — Create a new project.19- `mcp__vercel__vercel_delete_project` — Delete a project.2021## Workflow2223When the user asks you to create and deploy a website:24251. **Build the content in memory** — Compose HTML/CSS/JS as strings. Do NOT write files to disk first.262. **Deploy directly** — Pass the strings straight to `mcp__vercel__vercel_deploy`:27 - `name`: project name (lowercase, hyphens only)28 - `files`: array of `{file: "path", data: "content"}` objects — `data` is the raw file content as a string29 - `projectSettings`: only set when using a known framework (see below). **For plain HTML/CSS/JS sites, do NOT pass `projectSettings` at all.**303. **Return the URL** — The deploy tool returns a URL. Share it with the user.3132**Important:** Do NOT write files to disk and then read them back to pass to the deploy tool. This causes unnecessary read/escape loops. Build the content and pass it directly to `data`.3334## Example3536For a simple static site:3738```39mcp__vercel__vercel_deploy({40 name: "my-site",41 files: [42 { file: "index.html", data: "<html>...</html>" },43 { file: "style.css", data: "body { ... }" }44 ]45})46```4748## Critical: `projectSettings.framework` rules4950The Vercel API will **reject the deploy with a 400 error** if `projectSettings.framework` is not an exact match from the allowed list. To avoid this:5152- **Plain HTML/CSS/JS sites** → Do NOT include `projectSettings` at all. Omit it entirely. Vercel auto-detects static sites.53- **Known frameworks only** → Only set `framework` if the project actually uses one of these: `nextjs`, `vite`, `astro`, `remix`, `svelte`, `sveltekit`, `nuxtjs`, `gatsby`, `vue`, `angular`, `create-react-app`, `solidstart`, `hugo`, `jekyll`, `eleventy`, `redwoodjs`.54- **When in doubt** → Omit `projectSettings`. It is always safer to let Vercel auto-detect than to guess a framework value.5556## Notes5758- Each deploy creates a unique URL. The latest deploy is also available at `<project-name>.vercel.app`.59- If VERCEL_API_TOKEN is not set, all tools will fail with an error.
yukihirop