mcpField
D
deployport

deployport

Local
github.com/CloudCorpRecordsCloud & Infra0Updated 2w ago
Repository

About deployport

deployport is a token-based MCP server and CLI for managing a core subset of Vercel project and deployment operations through the Vercel REST API. It includes project and deployment queries, deployment creation and cancellation, domain listing, and environment-variable reads.

Key features

  1. 01List, view, create, and delete projects
  2. 02List, view, create, and cancel deployments
  3. 03List domains and deployment events
  4. 04Read project environment variables
  5. 05Optional team-scoped API requests

Use cases

  1. 01Inspect Vercel projects and deployments
  2. 02Create or cancel a deployment
  3. 03Review deployment events and project environment variables

MCP support

Exposes Vercel REST API operations as MCP tools, using a Vercel API token. The server runs over stdio.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "cloudcorprecords-deployport": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/deployport"
      ]
    }
  }
}
Run commandnpx -y @reneturcios/deployport

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@reneturcios/deployport0.1.0
ocighcr.io/cloudcorprecords/deployport:0.1.0

Tools

12

Saved tool list · updated 1w ago

ParameterTypeRequiredDescription
limitnumberNoMaximum number of projects to return.

Details

From the project README

deployport

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.

Tools (core subset, 12)

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.

Setup

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.

CLI

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.

MCP client config

{
  "mcpServers": {
    "deployport": {
      "command": "npx",
      "args": ["-y", "@reneturcios/deployport", "mcp"],
      "env": { "VERCEL_TOKEN": "..." }
    }
  }
}

Docker

docker run -i -e VERCEL_TOKEN ghcr.io/cloudcorprecords/deployport

Development

npm install
npm run build
npm test

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.