Skip to content

Vercel Connector

The Vercel connector provides visibility into your Vercel deployments, projects, and domains with 8 live tools and ETL ingestion into the knowledge graph.

Authentication

Vercel uses an API token for authentication. Generate a token from your Vercel account settings.

json
{
  "name": "Production Vercel",
  "source_type": "vercel",
  "config": {
    "token": "vercel_xxxxxxxxxxxxxxxxxxxxxxxxxxxx",
    "team_id": "team_xxxxxxxxxxxxxxxxxxxxxxxx"
  }
}

Generating an API Token

  1. Go to Vercel Account Settings > Tokens
  2. Click Create Token
  3. Name it agentcy-connector
  4. Set the scope to your team (or personal account)
  5. Set expiration as appropriate (no expiration for persistent connectors)
  6. Copy the token immediately — it won't be shown again

TIP

If you are on a Vercel Team plan, include the team_id to scope the connector to your team. You can find it in Team Settings > General.

Live Tools (8)

ToolDescriptionArguments
vercel_list_projectsList all projects with framework, repo link, and latest deploymentteam_id?, limit?
vercel_get_projectGet detailed project informationproject_id
vercel_list_deploymentsList recent deployments with status, URL, and commit infoproject_id?, state?, limit?
vercel_get_deploymentGet detailed deployment info including build logs URLdeployment_id
vercel_list_domainsList domains with verification status and configurationproject_id?
vercel_get_domainGet detailed domain info including DNS recordsdomain
vercel_list_env_varsList environment variables for a project (values redacted)project_id, target?
vercel_list_aliasesList deployment aliases and custom domainsproject_id?, deployment_id?

Example: Agent Using Vercel Tools

User: "What's the latest deployment status for the frontend project?"

Agent: Let me check the recent deployments.
→ Calls vercel_list_deployments(project_id: "frontend", limit: 5)
→ Returns:
  1. dpl_abc123 — READY — https://frontend-abc123.vercel.app — 2m ago (main, abc1234)
  2. dpl_def456 — ERROR — https://frontend-def456.vercel.app — 45m ago (fix/header, def4567)
→ Reports: "The latest deployment on main is live and healthy.
   However, the previous deployment from the fix/header branch failed."

ETL Ingestion

Nodes Created

Node LabelPropertiesSource
VercelProjectname, framework, node_version, repo, created_at, updated_atProjects API
VercelDeploymentid, url, state, created_at, ready_at, commit_sha, commit_message, branchDeployments API
VercelDomainname, verified, configured_by, created_at, nameserversDomains API
VercelEnvVarkey, target, type (encrypted/plain/secret)Env Vars API

Relationships Created

RelationshipFromTo
HAS_DEPLOYMENTVercelProjectVercelDeployment
HAS_DOMAINVercelProjectVercelDomain
HAS_ENVVercelProjectVercelEnvVar
DEPLOYED_FROMVercelDeploymentRepository (GitHub connector)
ROUTES_TOVercelDomainVercelDeployment

Graph Queries

cypher
-- Find projects with failed recent deployments
MATCH (p:VercelProject)-[:HAS_DEPLOYMENT]->(d:VercelDeployment)
WHERE d.state = "ERROR"
AND d.created_at > datetime() - duration("P1D")
RETURN p.name, d.url, d.commit_message

-- Cross-connector: link Vercel deployments to GitHub PRs
MATCH (d:VercelDeployment)-[:DEPLOYED_FROM]->(r:Repository)-[:HAS_PR]->(pr:PullRequest)
WHERE d.commit_sha = pr.head_sha
RETURN d.url, pr.title, pr.author

-- Find projects without custom domains
MATCH (p:VercelProject)
WHERE NOT (p)-[:HAS_DOMAIN]->()
RETURN p.name

Configuration Reference

FieldTypeDefaultDescription
tokenstringrequiredVercel API token
team_idstring--Team ID to scope to (omit for personal account)
sync_deployments_depthint50Number of recent deployments to ingest per project
sync_env_varsbooltrueInclude environment variable metadata (values redacted)
sync_domainsbooltrueInclude domain data
include_projectsstring[]["*"]Project name patterns to include
exclude_projectsstring[][]Project name patterns to exclude

Troubleshooting

ErrorCauseFix
401 UnauthorizedInvalid or expired API tokenRegenerate the token in Vercel settings
403 ForbiddenToken does not have access to the teamVerify team_id and token scope
404 Not FoundProject or deployment does not existCheck the project ID or deployment ID
429 Rate LimitedToo many API requestsWait and retry; Vercel rate limits are per-token
TimeoutVercel API is slow to respondIncrease sync timeout or reduce sync_deployments_depth

Verifying Access

Test your token from the command line:

bash
# Verify token and list projects
curl -H "Authorization: Bearer vercel_xxxxx" \
  https://api.vercel.com/v9/projects

# Verify team access
curl -H "Authorization: Bearer vercel_xxxxx" \
  "https://api.vercel.com/v9/projects?teamId=team_xxxxx"

# List recent deployments
curl -H "Authorization: Bearer vercel_xxxxx" \
  https://api.vercel.com/v6/deployments?limit=5

Built by AgentcyLabs. For in-house deployment or Agentcy Cloud (PaaS) access, visit agentcylabs.com.