Question 1

What runtime and accounts are required?

Accepted Answer

Node.js 16 or later, npm 8 or later, a Vercel account with a valid access token (and optionally a Team ID or Project ID), and either Cursor IDE or Codeium Cascade for paying users.

Question 2

How do I debug or troubleshoot the server?

Accepted Answer

Add `DEBUG=true` before the command to see detailed logs. Common issues include incorrect Node.js path (use `which node` or `where node`), invalid or expired Vercel access token, or the MCP not detecting tools—refresh Cursor’s MCP settings or verify server is running without errors.

Question 3

How is the Vercel access token handled?

Accepted Answer

The token must be placed in both `src/config/constants.ts` and `src/index.ts`. Keep it secure, never commit it to version control, and ensure it has the required permissions.

Question 4

What transports and authentication does it use?

Accepted Answer

The server runs as a local MCP tool, started via a command line. Authentication is handled entirely by the Vercel access token passed in the configuration files; no additional transport layer is mentioned.

Question 5

Are there any known limits or scalability constraints?

Accepted Answer

The README does not specify rate limits, concurrency caps, or dataset size restrictions. For production use, follow Vercel’s security best practices and use appropriate access controls.

Vercel MCP Server

关于 Vercel MCP Server