Integrations · Development

Connect Vercel to Well

Link Vercel record, owner, and timestamp to the customer and revenue context they affect.

What Well pulls from Vercel

Vercel feeds record, owner, timestamp into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Vercel’s access.

From Vercel	In Well	Relation
Record	Graph node	Becomes
Owner	Team member	Resolves to
Timestamp	Audit entry	Anchors

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: Vercel → Well

What Well does with your Vercel connection

Connect

Connect Vercel over OAuth (MCP DCR): Well registers a client through Vercel's OAuth Dynamic Client Registration and you approve on Vercel's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings record, owner, and timestamp in from Vercel on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each Vercel entity into graph node, team member, and audit entry, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Vercel lands in the workspace as graph node, team member, and audit entry you can search, chart, and automate.

Questions Vercel unlocks

Ask in plain language. Well answers from your connected Vercel connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Vercel connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Vercel connection…

1 agent skill runs on Vercel.

Well lists Vercel in the connection check every skill runs before it answers. No skill reads it for a figure yet.

Connects and checks Vercel

Check your connections

See what is connected, what is syncing, and what is missing.

Browse all skills

Connect Vercel in three steps

01
Authorise Vercel via MCP
From Well's Connections panel, search for Vercel and click Connect. Well discovers Vercel's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Vercel's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.vercel.com
02
Map your entities
Well's MCP client discovers record, owner, and timestamp from Vercel that Vercel's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.
- Mappingpreconfigured by Well
03
Use the data
Ask questions in conversation, build records tables, or let agents act on Vercel records. Because Vercel ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.
- First syncstarts as soon as connect completes

MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical Vercel records happens in the background.

How Vercel stays secure with Well

Well connects to Vercel's MCP server (mcp.vercel.com) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Vercel secret. Tokens are scoped to the record, owner, and timestamp Vercel exposes and refreshed server-side. Reads only, Well cannot modify or delete Vercel records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.vercel.com

Read Vercel records
Resources the Vercel MCP server exposes, scoped by your OAuth approval.
granted
Resolve record, owner, and timestamp across your stack
Match identifiers in Vercel against the same entities your other connected tools expose, so each record carries cross-tool context.
granted
Modify or delete Vercel records
Not granted; Vercel is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store Vercel passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused

Disconnect any time from Well settings or Vercel’s admin panel.

Frequently asked questions about Vercel and Well

How do I connect Vercel to Well, and how long does it take?

From Well, open Connections, find Vercel, and click Connect. Well discovers the OAuth metadata at mcp.vercel.com/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Vercel's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

What does Well pull into the workspace from Vercel?

Well brings in record, owner, and timestamp from Vercel and reshapes each entity into your workspace: record becomes graph node; owner becomes team member. Every record arrives with the source identifier preserved, so Vercel stays the source of truth while Well lets you query the data alongside the rest of your stack.

How does Well link Vercel activity to customer or revenue context?

Well links Vercel activity (issues, commits, deploys, runs) to the customer accounts in your CRM that originated each request. A bug report from a top-revenue customer shows that revenue context inline; a deploy mentions the customer-facing features that just shipped.

What happens when Vercel updates a record that Well already pulled in?

Well watches for updates to records and applies them on the next sync, preserving the original workspace identifier so anything downstream (records tables, conversation history, agent runs) keeps pointing at the right graph node. Edits flow in incrementally; nothing is duplicated, and the Vercel source identifier is retained on every revision.

How often does Vercel sync with Well, and what triggers a refresh?

Well combines live Vercel events with periodic reconciliation reads of record, owner, and timestamp. New rows appear within seconds when Vercel pushes them; periodic reads catch anything a push missed. The first connect backfills history from Vercel in the background.

Can I disconnect Vercel and what happens to the data Well already pulled?

Open Connections > Vercel in Well and click Disconnect. Well calls Vercel's token revocation endpoint and stops calling Vercel immediately on its side; provider-side propagation to Vercel's admin panel varies by provider. The record, owner, and timestamp Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

How does Well protect what it pulls in from Vercel?

The Vercel records Well holds are encrypted at rest and handled in line with GDPR. See /privacy for the current data-handling policy.