Vercel Deployment MCP server

vercel-deployment-mcp

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

listprojects and listdeployments 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:

npm install @addiplus/vercel-deployment-mcp

Or run it directly without installing:

npx @addiplus/vercel-deployment-mcp

From source:

git clone https://github.com/addiplus/vercel-deployment-mcp.git
cd vercel-deployment-mcp
npm install
npm run build
npm 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

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

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.

Shortened. The full README is on GitHub.