Vercel

What it gives Plexward

• Deployment status for an entity's site, so a brief can say "the marketing site has an unpromoted preview from Tuesday".
• Preview URLs for review, which is how site changes get looked at before a human promotes them.
• Project and environment variable inventory, read-only, when you need to know what a project expects without opening a browser.

Layer

cli, with an optional plugin-provided MCP surface at the account layer. The vercel CLI holds one authenticated identity for the machine; scoping to an entity is done by which project directory you are in.

{ "name": "Vercel", "layer": "CLI/API", "svc": "Deployments", "account": "acme team (@you)" }

Prerequisites

• The vercel CLI installed.
• A Vercel account with access to the team that owns the entity's projects.
• The site repo cloned locally and linked to its Vercel project.

Setup steps

vercel login
cd ~/sites/acme-site
vercel link            # links this directory to the project
vercel whoami          # confirm the identity

Declare it in catalog/declarations.json and record the project name in the entity's brain.

Per-entity routing

## Owned Integrations
| Tool | Service | Account | Notes |
|---|---|---|---|
| Vercel (CLI) | Deployments | acme team | Project `acme-site`. Previews only from agents; promotion is human. |

## NOT This Company
- Vercel projects belonging to any other entity.

The rule worth writing down: agents deploy previews, humans promote. No skill or loop should run a production deploy or a promotion. Reviewing a preview URL is cheap; unpicking a bad production promotion is not.

Verify

vercel whoami
vercel project ls | head

Expected: your account name, and the entity's project in the list. If the plugin MCP surface is attached, claude mcp list will show it too, and a failing Needs authentication there means the plugin's own auth, not the CLI's.

Common failures

• The CLI is logged in and the MCP plugin is not. They authenticate separately. The probe can report the plugin red while vercel whoami is fine.
• Wrong team scope. A personal account and a team account both exist; a project invisible to vercel project ls usually means the CLI is scoped to the wrong one.
• A directory that was never linked. Commands run against nothing, or prompt interactively and hang in a headless run.
• Protected previews return 401 to automated checks. Deployment protection is on by default for some teams. Automated verification needs the documented access path rather than a plain request.

What Plexward does with it once connected

Site changes are built on a branch, deployed as a preview, and linked from the pull request. A brief can carry the preview URL so you can look at it from your phone. Production promotion stays a manual step you take after reviewing.