io.github.CloudCorpRecords/deployport is an MCP server that vercel projects, deployments, domains and env vars as MCP tools. Its tool list has not been published yet over stdio, requires no API key, and scores 56/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"deployport": {
"env": {
"VERCEL_TOKEN": "..."
},
"args": [
"-y",
"@reneturcios/deployport",
"mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Vercel projects, deployments, domains and env vars as MCP tools.
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
npx -y '@reneturcios/deployport' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @reneturcios/deployport against OSV.dev.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in devops
MCP server for using the GitLab API
MCP server for discovering, reading, and changing ZenML resources with compact generic tools
MCP server for Dynatrace Managed to access logs, events, and metrics.
An MCP server for Azure DevOps
MCP Security Weekly
Get CVE alerts and security updates for io.github.CloudCorpRecords/deployport and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Vercel projects and deployments as MCP tools, talking to the Vercel REST API. deployport is a clean-room rebuild of the core surface of the Vercel MCP server, under a new name: fresh code, no copied branding. The original is Vercel's official remote MCP (hosted OAuth); hosted OAuth is NOT reproduced — this rebuild is a token REST client for the same API.
list_projects, get_project, create_project, delete_project,
list_deployments, get_deployment, create_deployment,
cancel_deployment, list_domains, get_deployment_events,
list_project_env_vars, get_current_user.
Not in this subset: deployment creation from git/files depth (gitSource payloads, file uploads), env var create/update/delete writes, domains create/delete and DNS records, project settings depth (framework/build overrides, protection, aliases assignment), deployment promote/rollback, checks, integrations/marketplace, edge config, blob/firewall/observability products, team/member admin, billing.
Create an API token in Vercel and set it:
export VERCEL_TOKEN=...
Optionally override the API base with VERCEL_API_BASE_URL
(default https://api.vercel.com). Optionally scope every request
to a team with VERCEL_TEAM_ID; when set, a teamId query
parameter is appended to every request after the tool's own params.
Without the token, every tool call fails with an error naming the
missing variable.
npx @reneturcios/deployport list_projects '{"limit":10}'
npx @reneturcios/deployport mcp # stdio MCP server
Each tool name is a subcommand taking one JSON object argument.
{
"mcpServers": {
"deployport": {
"command": "npx",
"args": ["-y", "@reneturcios/deployport", "mcp"],
"env": { "VERCEL_TOKEN": "..." }
}
}
}
docker run -i -e VERCEL_TOKEN ghcr.io/cloudcorprecords/deployport
npm install
npm run build
npm test
MIT