Integrations · Development

Connect Vercel to Well

Connect Vercel to make it reachable from conversation and your agents in Well. Vercel exposes no structured records to sync today, so this is a reach connection, not a data feed.

Connect VercelSee what Well does

What Well pulls from Vercel

Vercel feeds Vercel 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
Vercel		Workspace context	Reachable from

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

Connecting Vercel makes it reachable from your workspace; Vercel exposes no structured records for Well to sync into the data model today.

Enrich

With no records to ingest, Vercel adds reach without enrichment; entity resolution and categorisation run for connectors that bring structured data in.

Available

Vercel is reachable from conversation and agents in your workspace; once it exposes structured records they land alongside the rest of your connected tools.

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…

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
Make it reachable
The connection puts Vercel within reach of your workspace and its agents. Vercel exposes no structured record for Well to map into an invoice, transaction, or account today, so there is no records table to set up and Well will not invent one to fill the step.
- Mappingnone (reach-only)
03
Use it from your workspace
Use the connection to let an agent reach Vercel in the same place it reaches the rest of your stack. If Vercel later exposes structured entities that map onto what Well captures, the data-flow section would reflect the real records.
- Availabilityreachable as soon as connect completes

This is a reach-and-availability connection, not a records feed, so nothing backfills.

How Vercel stays secure with Well

Well connects to Vercel's MCP server (mcp.vercel.com) via the Model Context Protocol. The MCP server handles credential issuance through OAuth Dynamic Client Registration, so Well never holds a long-lived Vercel secret. Because Vercel maps no structured entity today, the token simply makes Vercel reachable from your workspace rather than syncing records. The connection is read-only and grants Well nothing it could change in Vercel.

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
Reach Vercel from your workspace
The grant makes Vercel reachable from conversation and your agents. It maps no structured entity, so Well resolves no records and can change nothing in Vercel.
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?

Choose Vercel in Well's Connections panel and authorise it over its MCP server. Well discovers the OAuth metadata from the MCP endpoint and registers a client via Dynamic Client Registration, so there are no keys to paste. The handshake completes in about a minute and puts Vercel within reach of your workspace and its agents.

What does Well sync from Vercel today?

No structured record, and the page is candid about that. Vercel exposes no supported target model for Well to turn into an invoice, transaction, or account, so there is no records table to configure and nothing is pulled into your workspace. The connection is about reach, not a data feed.

If nothing is synced, what does connecting Vercel give me?

It lets an agent working in your workspace reach Vercel in the same place it reaches the rest of your stack, instead of treating it as a separate destination. This is a reach-and-availability connection: honest about not pulling structured records that Vercel does not expose.

Will Vercel ever bring records into the workspace?

Only if and when Vercel exposes structured entities through its MCP server that map onto what Well captures. Until then Well will not invent a synced record to make the page look fuller; if that changes, the data-flow section would reflect the real entities.

What happens if I disconnect Vercel?

Disconnecting Vercel in Well revokes the OAuth token and ends the MCP reach immediately. Because nothing structured was being synced, there are no workspace records to retain or purge; it simply removes Vercel from the set of tools your agents can reach through Well.