Product and engineering

The Vercel connector.

Projects, deployments, domains and build logs. Connect once with your own key. Every agent your team runs reads the same 5 tools under one permission model.

How access is governed

5

Read tools

Open by default. They run when called, and every call is logged with the endpoint, tool and capability.

0

Write tools

Vercel exposes no write tools. Nothing it does mutates external state.

0

Destructive tools

Vercel defines no destructive tools. Nothing here deletes data.

Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.

Every Vercel tool

5 tools, named as the agent sees them.

  • list_projectsread

    List Vercel projects in the configured scope. Use this first — a project `name` or `id` narrows list_deployments.

  • list_deploymentsread

    List recent deployments, newest first. Pass `project_id` (the project name or id from list_projects) to scope it. The returned `uid` feeds get_deployment and get_deployment_events.

  • get_deploymentread

    Get one deployment in full, including its build state and error detail. Takes the `uid` from list_deployments (a deployment URL also works).

  • get_deployment_eventsread

    Get the build log events for a deployment — use this to read why a build failed. Takes the `uid` from list_deployments, ideally one whose state is ERROR.

  • list_domainsread

    List the domains registered in the configured scope, with their verification state.

Use it from any agent

The same Vercel tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.

.mcp.json · works for Cursor and Claude Desktop too
{
  "mcpServers": {
    "growth": {
      "type": "http",
      "url": "https://app.notara.ai/mcp/g/acme/growth",
      "headers": {
        "Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

The URL and token are placeholders. Real endpoints are issued per group from the dashboard.

Setup

  1. 01

    Create a Vercel Access Token in your Vercel account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.

  2. 02

    Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.

  3. 03

    The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.

More in product and engineering

LinearCursorSentryAsanaClickUpNotion

Connect Vercel once. Use it everywhere.

Use Notara directly, or bring us the workflow that needs to be redesigned and built.

Book a callSign in