vercel-mcp-overview

Summary Add Antigravity to the client setup table in README (it was not listed among supported clients). Add with OAuth and Bearer-token configuration, verification steps, and troubleshooting for the common 406 Not Acceptable handshake failure. Motivation Antigravity uses Streamable HTTP with its own default header. Vercel MCP is strict about content negotiation; users who override or misplace auth ( vs ) see opaque 406 errors with no doc guidance. Addresses #1 Test plan [ ] JSON examples validate in Antigravity [ ] Link from README resolves to [ ] Consider mirroring this section on

Summary On 2026-10-02, Codex Desktop showed the Vercel MCP deployment action , but invoking it failed with . Other read-only Vercel actions were available and working; reconnecting and generating a fresh connection link did not change the result. Expected If a tool is advertised to Codex, it should execute. Otherwise, the integration should indicate that the tool is unavailable instead of returning a dispatch-level error. Context Client: Codex Desktop Server: Vercel MCP () No deployment was created, so there is no deployment ID. Related report: Vercel Community topic Could you confirm whether this is a server-side tool-registration issue, a Codex-specific support/configuration issue, or an unsupported operation?

Summary On the hosted Vercel MCP server (, connected from Claude Code 2.x as an HTTP MCP server), the tool cannot be called at all: its advertised input schema names the argument , but the handler validates a field called , so every call fails input validation before reaching the API. Repro 1. Add the server: , complete OAuth. 2. Call with the arguments the tool schema advertises: 3. Response: The tool's own schema (as listed by the server) is: There is no in it, so a client following the schema can never satisfy the validator. Passing instead is rejected by the client side (unknown argument). Expected Either the schema advertises (matching ), or the handler accepts . Environment Claude Code CLI (2026-09), HTTP transport, team-scoped OAuth Other tools on the same session work (, , , ), so this is specific to . Reproduced by two separate sessions/accounts on 2026-09-08 and 2026-09-19. Related: an env-var listing tool (names only, values redacted) would remove the need for the CLI in agent workflows; today was the only route to project metadata and it is broken.