Integrations · Development

Connect Arcade to Well

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

Connect ArcadeSee what Well does

What Well pulls from Arcade

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

From Arcade		In Well	Relation
Arcade		Workspace context	Reachable from

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

What Well does with your Arcade connection

Connect

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

Sync

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

Enrich

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

Available

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

Questions Arcade unlocks

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

Ask Well

Ask anything about your Arcade connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Arcade connection…

1 agent skill runs on Arcade.

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

Connects and checks Arcade

Check your connections

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

Browse all skills

Connect Arcade in three steps

01
Authorise Arcade via MCP
From Well's Connections panel, search for Arcade and click Connect. Well discovers Arcade's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Arcade's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
02
Make it reachable
The connection puts Arcade within reach of your workspace and its agents. Arcade 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 Arcade in the same place it reaches the rest of your stack. If Arcade 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 Arcade stays secure with Well

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

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requests

Read Arcade records
Resources the Arcade MCP server exposes, scoped by your OAuth approval.
granted
Reach Arcade from your workspace
The grant makes Arcade reachable from conversation and your agents. It maps no structured entity, so Well resolves no records and can change nothing in Arcade.
granted
Modify or delete Arcade records
Not granted; Arcade is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store Arcade passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused

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

Frequently asked questions about Arcade and Well

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

Choose Arcade 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 Arcade within reach of your workspace and its agents.

What does Well sync from Arcade today?

No structured record, and the page is candid about that. Arcade 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 Arcade give me?

It lets an agent working in your workspace reach Arcade 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 Arcade does not expose.

Will Arcade ever bring records into the workspace?

Only if and when Arcade 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 Arcade?

Disconnecting Arcade 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 Arcade from the set of tools your agents can reach through Well.