Vercel Deployment Mcp

io.github.addiplus由 GitHub 帳號 addiplus 發布v0.2.0更新於 Oct 24, 2026

Reference MCP stdio server for observing Vercel projects and deployments.

發布方自己的服務:Agent Permissions Index

概覽

AI 產生的概覽

一個本機 stdio MCP 伺服器,讓助理使用 Vercel API 權杖讀取 Vercel 專案與部署資訊。

可以做什麼
列出設定帳號或團隊可見的專案,支援搜尋與數量限制,並依 ID 或名稱取得單一專案。列出近期部署,可依專案、狀態或數量篩選,並依 ID 或 URL 取得單一部署及其目前狀態。結果每次只回傳一頁,最多 100 筆,沒有游標分頁,需要更精確的結果時應縮小篩選條件。
適用情境
適合在除錯或檢視發佈時讓助理查詢 Vercel 專案與部署狀態,而不必開啟 Vercel 主控台。它是小型的社群參考實作,並非 Vercel 官方 MCP 服務的替代品。
執行需求
透過 stdio 在本機執行,通常用 npx 從 npm 套件啟動,或從原始碼取出後以 Node.js 18 以上版本執行。需要在 VERCEL_TOKEN 環境變數中提供 Vercel API 存取權杖;VERCEL_TEAM_ID 為選用,用於團隊範圍。選用的流量限制設定為 VERCEL_MCP_MIN_INTERVAL_MS 與 VERCEL_MCP_MAX_CONCURRENT。需要連線至 Vercel API 的網路。
安裝前請注意
Vercel API 權杖屬於憑證,只應放在環境變數中,避免分享含有它的設定。工具被描述為唯讀查詢,但權杖本身的權限決定可存取的範圍。Vercel 回傳的部署 URL 可能包含團隊識別碼。請求會傳送給第三方 Vercel API。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Vercel Deployment Mcp,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

vercel-deployment-mcp

[CI]

A reference Model Context Protocol server for observing Vercel projects and deployments over stdio.

This is a community reference implementation focused on deployment-workflow patterns. It is not a replacement for Vercel's own MCP offering. Its purpose is to demonstrate, in a small and readable codebase, how a deployment-focused MCP server can handle configuration cleanly and behave predictably on short-lived infrastructure.

Tools

ToolDescription
list_projectsList projects visible to the configured account/team (search, limit)
get_projectFetch one project by ID or name
list_deploymentsList recent deployments (filter by project, state, limit)
get_deploymentFetch one deployment by ID or URL, including current state

list_projects and list_deployments each return a single page of up to limit results (default 20, max 100). There is no cursor pagination; narrow the request with search, projectId, or state to see more specific results.

Install

From npm:

bash
npm install @addiplus/vercel-deployment-mcp

Or run it directly without installing:

bash
npx @addiplus/vercel-deployment-mcp

From source:

bash
git clone https://github.com/addiplus/vercel-deployment-mcp.gitcd vercel-deployment-mcpnpm installnpm run buildnpm test

Running the test suite needs a newer Node than the server does. vitest 4.1.10 declares engines.node of ^20.0.0 || ^22.0.0 || >=24.0.0, and the vite 8.1.3 this lockfile pins narrows that to ^20.19.0 || >=22.12.0. The suite runs on the intersection of the two, ^20.19.0 || ^22.12.0 || >=24.0.0: the 20 line from 20.19.0, the 22 line from 22.12.0, and 24 and above. The 23 line is outside it, because vitest does not cover 23. CI runs 22 and 24. The published package itself still runs on Node >=18 per engines.

Configuration

VariableRequiredPurpose
VERCEL_TOKENyesVercel access token (create in account settings)
VERCEL_TEAM_IDnoScope requests to a team
VERCEL_MCP_MIN_INTERVAL_MSnoMinimum milliseconds between the start of one Vercel API request and the next (default 250)
VERCEL_MCP_MAX_CONCURRENTnoMaximum number of Vercel API requests in flight at once (default 4)

On an HTTP 429 with a numeric Retry-After header of 10 seconds or less, the server waits that long and retries the request once; any other 429 is surfaced as an error on the first attempt.

Limits

LimitValue
Longest search value4096 characters
Longest projectId, state, idOrName, idOrUrl value512 characters
Largest accepted protocol frame10485760 bytes
Highest accepted VERCEL_MCP_MIN_INTERVAL_MS60000

The frame limit counts the message and not the newline that delimits it, so a message of exactly 10485760 bytes is accepted. Everything before that newline is the message, a carriage return sitting just in front of it included.

Each of these limits has its own behaviour above the value in the table. An over-long argument fails input validation: the call comes back as a JSON-RPC -32602 invalid-params result, no Vercel API request is made, and nothing is written to stderr for it. A frame above the frame limit is dropped, one line on stderr says so, and the connection keeps serving. An interval above the ceiling is not refused, it is reduced to the ceiling: the server runs with the reduced value, and one line on stderr says so the first time it makes a Vercel API request. The same stderr report repeated back to back is written twice at most, the second time to say that further identical reports are suppressed.

initialize and ping are answered at any time. tools/list and tools/call are answered only once the client has completed the initialization handshake: an initialize request the server can answer, followed by notifications/initialized. Both halves are required, so the notification on its own completes nothing, and neither does an initialize the server rejects. A client that writes both halves and its first call in a single write is served, rather than being refused for not waiting for the initialize response. Before the handshake, those two methods are refused with JSON-RPC error -32600 and no Vercel API request is made.

Example client configuration (Claude Desktop / Claude Code):

json
{  "mcpServers": {    "vercel-deployment": {      "command": "npx",      "args": ["-y", "@addiplus/vercel-deployment-mcp"],      "env": { "VERCEL_TOKEN": "…" }    }  }}

When running from a source checkout, use "command": "node" with "args": ["/path/to/vercel-deployment-mcp/dist/index.js"] instead.

Design principles

First written 2026-07-10 and kept current with the code since; claim 1 was restated when error text began being redacted once, where it becomes client-visible. Each claim below is implemented in code and verified by the test suite where testable (test/); design properties cite the implementing code.

  1. Configured values never appear in an error. The access token is read only from the environment. Error text is shaped, size-bounded, and passed through a redaction guard once, where it becomes client-visible text, so an upstream API message cannot echo the token or the team id back (src/vercel.ts); the fixed hint appended after that bound is text this server writes and carries nothing to replace. A successful result is a fixed projection of the upstream body and is not redacted, so a team identifier that the Vercel API itself returns inside a deployment URL still appears there.
  2. stdout belongs to the protocol. All diagnostics go to stderr (src/index.ts), so no log line can leak into a tool response.
  3. Minimal footprint. The tools are read-only observations of projects and deployments; the server requests nothing beyond what those reads need.
  4. Stateless by design. Configuration is re-read from the environment on every tool call (verified in test/tools.test.ts), so behavior is identical on long-lived hosts and short-lived workers. The one piece of module-level state is a request throttle (src/vercel.ts) that spaces out and caps concurrent Vercel API calls; its interval and concurrency settings are read once at first use, and it holds no credentials or response data.

Roadmap

  • Deployment actions with an explicit out-of-band approval step (exploring the patterns discussed in MCP spec issues #2919/#2920 around multi-round tool results on stateless transports).
  • Standardizing how server.json describes stdio package install manifests and how clients convert them into local configuration files (spec issue #2963, registry issue #749).

License

MIT

來源:README.md,提交 6911b5b

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.2.0最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Vercel 整合