Vercel

Vercel OAuth · Live

Inspect deployments without leaving the thread.

Connect Vercel via OAuth and ask the agent about deployment status, build errors, and Web Analytics metrics without leaving the thread.

Connect VercelHow it worksLive
Auth
Vercel OAuth
Access
Read-only
Plan
Every plan
Freshness
Live — every call hits the Vercel API
Available on
Every plan

Examples

Questions teams actually ask.

The tools it pulls from are shown inline — every answer in Lumen cites the underlying records it read.

Engineering

Which of the last 10 deployments failed, and what does the build log say?

pullsdeploymentsdeploymentLogs
On-call

The latest deploy to production is stuck on `BUILDING`. What's in its logs?

pullsdeploymentsdeploymentLogs
Product

What are the top 10 pages by visitors over the last 7 days, and what's the referrer mix?

pullswebAnalytics
Release

Summarise every deployment today, grouped by target, with durations.

pullsdeploymentsdeployment
Engineering

Which commit SHA is live on production right now?

pullsdeploymentsdeployment

Preview

See what the answer looks like.

Toggle the tools Lumen is allowed to use. The plan, answer, and cited sources update to match.

Tools
Read-only
You

Why did the last deploy to production fail?

Plan
  1. vercel.listDeployments — filter state=ERROR, limit 5
  2. vercel.getDeployment — pull errorMessage and domains for the latest
  3. vercel.getDeploymentLogs — tail build log for the failed deployment
  4. cross-reference commit SHA with GitHub for context
Answer

The last production deploy (dpl_9b2f...) failed after 2m 14s on `npm run build` — Next.js rejected the route `/api/agent` because a client component imported from a server-only file. The commit was a52f11c by @rob. I've inlined the relevant log lines below.

Sources
  • [1]vercel.listDeployments — 5 deployments, 1 with state=ERROR
  • [2]vercel.getDeployment — build duration, commit SHA, error message
  • [3]vercel.getDeploymentLogs — 412 log events, error block surfaced

Scope

What Lumen sees. What it can change.

Read is on by default. Every write is a separate toggle, capped per user, and logged.

Read

What Lumen reads

Lumen hits the Vercel REST API directly. Every call is scoped to the team and (optionally) project configured on the integration.

  • Deployments list

    Filterable by state: BUILDING, READY, ERROR, CANCELED, QUEUED, INITIALIZING

  • Deployment detail

    Build duration, target, domains, commit metadata, error message

  • Build logs

    Newline-delimited log events; large logs are streamed

  • Web Analytics

    Page views, visitors, top pages, top referrers over 24h / 7d / 30d / 90d

Write · opt-in

What Lumen can write

Lumen does not write to Vercel. No triggers, redeploys, env-var changes, or project-settings modifications. Read-only by design.

    Every read is logged with user, operation, project ID, and deployment ID (where relevant). Exportable as CSV.

    Install

    Connect in under a minute.

    No keys, no call, no app marketplace fine print.

    1. Connect
      01

      Sign in with Vercel

      In Settings → Integrations → Vercel, click Connect Vercel. You'll land on Vercel's standard OAuth screen to approve Lumen. Optionally configure a default team and project so the agent doesn't have to guess.

    2. Or paste a token
      02

      Use an API token instead

      Prefer an API token? Create one in your Vercel account settings and paste it — same scope, no OAuth round-trip.

    3. Ask
      03

      Try a warm-up question

      Start with "What are the last 5 deployments?" or "Any failed builds in the last hour?" — the agent will pick up the default project automatically.

    Questions

    Frequently asked.

    Does Lumen trigger redeploys?
    No. The integration is read-only. If you need to trigger a deploy, do it from the Vercel dashboard or CLI — we'll tell you which commit SHA the agent was looking at.
    Does Web Analytics need to be on?
    Yes — for `vercel.getWebAnalytics` to work you need Web Analytics enabled on the project. If it isn't, Lumen surfaces a clean error telling you to enable it in the Vercel dashboard.
    How does Lumen know which project to inspect?
    If you configured a default `projectId` at install, that's used. Otherwise the agent either asks, or infers from the conversation context (for example, if you're already discussing a deployment URL).
    What about deployment logs for serverless functions?
    `getDeploymentLogs` returns build events (the log stream from `npm run build` and friends). Runtime function logs are accessible via Vercel's runtime-logs endpoints — roadmap.
    Are Vercel teams supported?
    Yes. Set `teamId` on the integration and every call is scoped to that team.
    What about Preview Deployments?
    Every deployment is accessible — production, preview, and development. Filter by `target` in the detail response.

    Pairs with

    Better together.

    Connect Vercel. See every deploy.

    OAuth or API token. Read-only. No write scopes required.

    Connect VercelBack to all integrations