Vercel's MCP server has 33 tools. Four spend your money. None read your bill.

Vercel ships an official MCP server at mcp.vercel.com. It is well-built, OAuth secured, and works with Claude Code, Cursor, ChatGPT, Codex, VS Code Copilot and most other clients.

This is an independent audit of what it can and cannot do, because the gap is more interesting than the feature list.

What the 33 tools cover#

Grouped by what they are for:

• Documentation — search and retrieve Vercel docs.
• Projects — list, inspect, and manage projects and their configuration.
• Deployments — list deployments, inspect status, retrieve details.
• Logs — fetch and analyse build and runtime logs.
• Web Analytics — query visitor analytics.
• Teams — team and membership management.
• Purchasing — buy_pro, buy_credits, buy_addon, buy_domain, and get_purchase_quote.

It is a good set for what it is aimed at: letting an agent understand and operate your projects.

The asymmetry#

Read that purchasing line again, then consider what is absent.

An AI agent connected to Vercel's official MCP server can upgrade you to Pro, buy credits, buy add-ons and buy a domain. The same agent, asked "how much have I spent this month?", has no tool that can answer.

It can spend. It cannot account.

For a category of software whose entire failure mode is unattended processes running up costs, that is a strange place to land — and it is not an oversight of capability, because the underlying API exists.

The API that exists but is not exposed#

On 19 February 2026 Vercel shipped billing and usage cost data access:

• A /billing/charges endpoint, following the FOCUS v1.3 open standard, returning JSONL with 1-day granularity over a range of up to a year.
• A vercel usage CLI command with --from, --to, --breakdown and --format json.

Vantage built a native Vercel cost integration off the back of it. It is a real, complete, well-designed API.

It is also read-only and after-the-fact. No watch mode, no thresholds, no alerts, no pause. And it is not wired into the MCP server.

Why this matters more every month#

The reason to care is not tidiness. It is that the way people build is changing, and the cost model has not caught up.

Agents now run long unattended sessions — deploying, retrying, regenerating. A retry loop written by an agent bills exactly like a retry loop written by a human, except nobody is watching the terminal. The tooling that would let the agent check its own spending is the tooling that does not exist.

AWS and Azure both shipped official cost-management MCP servers in 2025. The category is established and understood. For Vercel and Netlify specifically, it is empty.

What we did about it#

MONII's MCP server is free, open source, and exists precisely to fill this gap. Three tools:

• monii_get_billing_status — current spend and usage across Vercel and Netlify.
• monii_read_unified_logs — build logs across both providers.
• monii_trigger_kill_switch — pause a project.

It runs locally against ~/.monii/auth.json, written by the open-source CLI. Your tokens do not go anywhere except to the provider APIs.

{
  "mcpServers": {
    "monii": {
      "command": "node",
      "args": ["./packages/mcp/dist/index.js"]
    }
  }
}

Sources#

• Vercel MCP documentation — the tool list.
• Vercel changelog: billing and usage cost data API — 19 February 2026.
• vercel usage CLI reference.

Questions people actually ask