Deployport

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026

Vercel projects, deployments, domains and env vars as MCP tools.

VerifiedSTDIODesktop onlyCloud & Infrastructure

Overview

Deployport's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open Deployport in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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:

bash
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

bash
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

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

Docker

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

Development

bash
npm installnpm run buildnpm test

License

MIT

Source: README.md at commit af7a84e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestNov 3, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts