Deployport runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 2 Nov 2026.
Vercel projects, deployments, domains and env vars as MCP tools.
Today is the operative word: we check Deployport every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add deployport -- npx -y @reneturcios/deployport
{
"mcpServers": {
"deployport": {
"command": "npx",
"args": [
"-y",
"@reneturcios/deployport"
]
}
}
}
[mcp_servers.deployport]
command = "npx"
args = ["-y", "@reneturcios/deployport"]
{
"mcpServers": {
"deployport": {
"command": "npx",
"args": [
"-y",
"@reneturcios/deployport"
]
}
}
}
{
"servers": {
"deployport": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/deployport"
]
}
}
}
Complete Vercel MCP: deploys, logs, projects, env, domains, DNS, certs via the full REST API
Reference MCP stdio server for observing Vercel projects and deployments.
Render services, deploys, env vars and logs as MCP tools.
Query the Vercel API (token; set VERCEL_TOKEN, Bearer): projects, project details, deployments.
Deploy apps and databases on Skiffly: projects, services, deployments, logs, variables, domains.
MCP server for the Google Apps Script API: projects, code, versions, deployments and executions.
Expose Fascia-deployed Tools and Entity schemas to AI agents via MCP
Manage the Massdriver infrastructure platform: projects, environments, deployments, and more.
Answers built from our own checks of this server.