Integrations · Development

Connect Alpic to Well

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

Connect AlpicSee what Well does

What Well pulls from Alpic

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

From Alpic		In Well	Relation
Alpic		Workspace context	Reachable from

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

What Well does with your Alpic connection

Connect

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

Sync

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

Enrich

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

Available

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

Questions Alpic unlocks

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

Ask Well

Ask anything about your Alpic connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Alpic connection…

1 agent skill runs on Alpic.

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

Connects and checks Alpic

Check your connections

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

Browse all skills

Connect Alpic in three steps

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

Well connects to Alpic'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 Alpic secret. Because Alpic maps no structured entity today, the token simply makes Alpic reachable from your workspace rather than syncing records. The connection is read-only and grants Well nothing it could change in Alpic.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requests

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

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

Frequently asked questions about Alpic and Well

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

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

What does Well sync from Alpic today?

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

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

Will Alpic ever bring records into the workspace?

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

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