Deploy MCP
Enables AI coding assistants to deploy websites directly to Vercel from the IDE, automating framework detection, build validation, and secure environment variable synchronization, with live status updates.
README
<div align="center">
š Deploy MCP
Deploy any website to Vercel ā straight from your AI IDE, in seconds.
Free. Open source. Zero server costs. Built for vibe coders.
Quick Start ⢠IDE Setup ⢠Tools ⢠Troubleshooting ⢠Contributing
</div>
⨠What is Deploy MCP?
Deploy MCP is a free, open-source MCP (Model Context Protocol) server that lets your AI coding assistant (Cursor, VS Code, Antigravity, etc.) deploy your website to Vercel automatically ā with full environment variable syncing, build validation, and git safety checks.
Just say "Deploy this" in your AI chat. That's it.
You: "Deploy this website."
AI: ā Next.js detected
ā Build check passed
ā Environment variables verified (secrets never exposed)
ā Deployed to Vercel
š Live at: https://my-portfolio.vercel.app
ā” Quick Start ā Deploy in 3 Steps
Step 1 ā Run Setup (one-time only)
Open your terminal and run:
npx @tusharjain-19/deploy-mcp setup
This will:
- Ask you for your Vercel Personal Access Token (see how to get it below)
- Save it securely on your machine
- Print the exact config to paste into your IDE
How to get your Vercel Token:
- Go to vercel.com/account/tokens
- Click "Create Token"
- Name it anything (e.g.
deploy-mcp)- Set scope to Full Access
- Copy the token and paste it when the setup wizard asks
Step 2 ā Add to Your IDE
Copy the right config for your IDE and add it to your settings file:
Cursor
File location: %APPDATA%\Cursor\User\settings\cursor_settings.json (Windows) or ~/.cursor/rules/cursor_settings.json (Mac/Linux)
{
"mcpServers": {
"deploy": {
"command": "npx",
"args": ["-y", "@tusharjain-19/deploy-mcp"],
"disabled": false
}
}
}
VS Code + Claude Extension
File location: settings.json (Ctrl+Shift+P ā "Open Settings JSON")
{
"claude.mcp.servers": [
{
"name": "deploy",
"command": "npx",
"args": ["-y", "@tusharjain-19/deploy-mcp"]
}
]
}
Antigravity (VS Code + Antigravity AI)
File location: settings.json (Ctrl+Shift+P ā "Open Settings JSON")
{
"claude.mcp.servers": [
{
"name": "deploy",
"command": "npx",
"args": ["-y", "@tusharjain-19/deploy-mcp"]
}
]
}
ā Restart your IDE after saving the config.
Step 3 ā Deploy!
Open your project folder in your IDE and tell the AI:
"Deploy this website"
The AI handles everything from there:
1. Scans your project ā Detects Next.js / React / Vue / etc.
2. Runs build check ā Makes sure your code compiles
3. Checks git status ā Warns if files aren't committed
4. Scans environment variables ā Keys only, values NEVER exposed to AI
5. Syncs missing env vars ā Uploads secrets directly to Vercel
6. Deploys to Vercel ā Triggers the actual deployment
7. Polls until live ā Waits and confirms it's up
8. Returns your live URL š
š Version Control (Git) ā Built In
Deploy MCP has full Git support built in. Your AI can:
| What it does | Command to ask AI |
|---|---|
| Check uncommitted changes | "Check my git status" |
| Commit & push before deploy | "Commit my changes and deploy" |
Detect leaked .env files |
"Check if my .env is in git" |
Best practice: Always commit your code before deploying. Ask the AI: "Commit my changes with message 'fix: update homepage' and then deploy"
The git tools work automatically during deployment ā if you have uncommitted changes, the AI will warn you and ask if you want to commit first.
š§° Available Tools
Your AI has access to 16 tools across 4 modules:
š¦ Project Tools
| Tool | What it does |
|---|---|
smart_deploy |
All-in-one deploy ā detects, checks, syncs env, deploys, polls, and auto-diagnoses failures |
detect_project |
Detects framework (Next.js, React, Vue, etc.) and build config |
check_project |
Validates the project can build successfully |
project_report |
Full pre-flight report ā git, build, env, everything |
delete_project |
Permanently deletes a Vercel project (requires your manual approval via OS popup) |
š Environment Variable Tools
Security: Secret values never reach the AI. Only key names are shown. Values go directly from your machine to Vercel.
| Tool | What it does |
|---|---|
scan_env |
Lists all local .env variables (names only, values hidden) |
compare_env |
Shows what's missing on Vercel vs. your local .env |
sync_env |
Uploads missing secrets directly from your machine to Vercel |
create_env_example |
Generates a safe .env.example file with all values blanked out |
validate_environment_variables |
Checks your local env against .env.example requirements |
check_env_leak |
šØ Detects if any .env files are accidentally tracked by Git |
šæ Git Tools
| Tool | What it does |
|---|---|
git_status |
Shows branch, uncommitted files, and change count |
git_commit_and_push |
Commits all changes and pushes to remote |
āļø Vercel Tools
| Tool | What it does |
|---|---|
deploy_to_vercel |
Triggers deployment |
get_deployment_status |
Polls current deployment status |
get_deployment_logs |
Fetches raw build logs for debugging |
diagnose_build_failure |
Parses logs and gives AI-readable fix suggestions |
š Troubleshooting
ā "Vercel not authenticated" or token error
npx @tusharjain-19/deploy-mcp setup
Re-run setup and paste a fresh token. Make sure the token has Full Access scope.
ā "MCP not showing up in my IDE"
- Double-check the JSON config you pasted ā look for missing commas or brackets
- Fully restart your IDE (close all windows, reopen)
- Test the server manually:
You should see:npx @tusharjain-19/deploy-mcpDeploy MCP server running on stdio
ā "Build failed" during deployment
Ask your AI: "Diagnose the build failure and fix it" ā the diagnose_build_failure tool will automatically parse the error logs and tell the AI exactly what to fix.
Common causes:
- Missing
npm installā runnpm installin your project - Wrong Node.js version ā add
"engines": { "node": "20" }topackage.json - Missing environment variable ā ask AI to sync your env vars
ā "Environment variables not syncing"
- Make sure your Vercel token has Full Access permissions
- Check that the project name you tell the AI exactly matches your Vercel project name
- Run: "Compare my local env vars with Vercel" ā the AI will show exactly what's missing
ā ".env file accidentally in Git"
Ask your AI: "Check if my .env is tracked by git"
The check_env_leak tool will detect it. If found, fix it:
# Remove .env from git tracking (keeps the file locally)
echo ".env" >> .gitignore
echo ".env.local" >> .gitignore
git rm --cached .env
git rm --cached .env.local
git commit -m "fix: remove .env from git tracking"
ā "Module not found" error locally
npm install
npm run build
ā "Cannot find Vercel CLI"
Deploy MCP uses the Vercel REST API directly ā no Vercel CLI needed. But if you want the CLI anyway:
npm install -g vercel
āļø How It Works
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā Your IDE (Cursor / VS Code / Antigravity) ā
ā ā
ā You say: "Deploy this" ā
āāāāāāāāāāāāāāāāāāāāā¬āāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā MCP Protocol (stdio)
ā¼
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā Deploy MCP Server (runs on YOUR machine) ā
ā ā
ā āāā detect_project() ā Read package.json ā
ā āāā check_project() ā Run build locally ā
ā āāā scan_env() ā Read .env names only ā
ā āāā sync_env() ā Push secrets directly ā
ā āāā deploy_to_vercel() ā Trigger deployment ā
āāāāāāāāāāāāāāāāāāāāā¬āāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā Vercel REST API
ā¼
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā Vercel ā
ā āāā Finds or creates your project ā
ā āāā Receives encrypted env vars ā
ā āāā Builds your site ā
ā āāā Returns your live URL š ā
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
Security Model
ā INSECURE (secret touches the AI):
.env ā AI Model ā MCP ā Vercel
ā
DEPLOY MCP (secret never leaves your machine):
.env ā MCP Process ā Vercel API
ā
AI sees key NAMES only, never values
š§ Development Setup
Want to run Deploy MCP locally from source?
# 1. Clone the repo
git clone https://github.com/Tusharjain-19/deploy-mcp.git
cd deploy-mcp/mcp-server
# 2. Install dependencies
npm install
# 3. Build TypeScript
npm run build
# 4. Run setup wizard
npm run setup
# 5. Start the server (IDEs do this automatically)
npm run dev
Test All Tools Without an IDE
npx @modelcontextprotocol/inspector npx tsx src/index.ts
This opens a browser UI where you can call every tool manually and see outputs.
Available Scripts
| Script | Command | Description |
|---|---|---|
| Build | npm run build |
Compile TypeScript to dist/ |
| Dev | npm run dev |
Run server directly with tsx |
| Setup | npm run setup |
Run the setup wizard |
š Project Structure
mcp-server/
āāā src/
ā āāā index.ts ā MCP server entry (all 16 tools registered)
ā ā
ā āāā tools/
ā ā āāā smart-deploy.ts ā All-in-one deploy with auto-diagnose
ā ā āāā check-project.ts ā Build validation
ā ā āāā deploy.ts ā Vercel deployment trigger
ā ā āāā diagnose.ts ā Build failure diagnosis
ā ā āāā env-vars.ts ā .env scanning, diffing, syncing
ā ā āāā git.ts ā Git status, commit, leak detection
ā ā āāā logs.ts ā Deployment log fetching
ā ā āāā delete-project.ts ā Safe project deletion with OS prompt
ā ā āāā project-report.ts ā Master pre-flight report
ā ā
ā āāā vercel/
ā ā āāā client.ts ā Vercel REST API wrapper
ā ā
ā āāā utils/
ā ā āāā config.ts ā Token storage/retrieval
ā ā āāā filesystem.ts ā File reading utilities
ā ā āāā framework-detector.ts ā Framework & package manager detection
ā ā
ā āāā cli/
ā āāā index.ts ā CLI entry point
ā āāā setup.ts ā Interactive setup wizard
ā
āāā dist/ ā Compiled JS (auto-generated, git-ignored)
āāā package.json
āāā tsconfig.json
āāā README.md
šŗ Roadmap
| Version | Status | Features |
|---|---|---|
| v1.0 | ā Done | Project detection, build check, Vercel deployment, status polling |
| v1.5 | ā Done | Env scanning (no leakage), env diff, env sync, git tools, project report |
| v1.6 | ā Done | Smart deploy (auto-diagnose failures), safe project deletion |
| v2.0 | š Planned | AI error auto-fix loop, preview deployments, rollback |
| v3.0 | š Future | Netlify/Railway support, GitHub integration, team deployments |
š Automatic Updates
Because your IDE config uses npx -y @tusharjain-19/deploy-mcp, Node.js will automatically pull the latest version from npm every time your IDE starts the server. No manual update commands needed ā you always get the latest features and fixes automatically.
š¤ Contributing
Contributions are welcome! This is a free, open-source project built for the community.
# Fork the repo, then:
git clone https://github.com/YOUR-USERNAME/deploy-mcp.git
cd deploy-mcp/mcp-server
npm install
# Create a feature branch
git checkout -b feature/my-feature
# Make changes, then build and test
npm run build
# Commit and push
git commit -m "feat: add my feature"
git push origin feature/my-feature
# Open a Pull Request on GitHub
Please open an issue first for large changes. Bug fixes and docs improvements are always welcome!
š Security
| Principle | How it's implemented |
|---|---|
| Secrets never touch the AI | scan_env returns only key names + classifications |
| No external servers | MCP runs entirely on your machine |
| No overwrite without consent | sync_env skips existing Vercel vars by default |
| Leak detection | check_env_leak scans git ls-files before deploy |
| Token stored locally | ~/.deploy-mcp/config.json ā your machine only |
| No hardcoded credentials | Zero hardcoded tokens in the codebase |
šØāš» About
Built by Tushar Jain ā tools that bridge the gap between AI and shipping real products.
- š tusharjain.in
- š @Tusharjain-19
š License
MIT License ā 100% free forever. Use it in commercial projects, modify it, distribute it. See LICENSE for full text.
<div align="center">
Built with ā¤ļø for vibe coders everywhere
ā Star this repo if it saved you time!
</div>
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.