Integrations · Content

Connect Lumin to Well

Index Lumin Lumin MCP server so your agents can search across them alongside the rest of your workspace.

What Well pulls from Lumin

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

From Lumin		In Well	Relation
Lumin MCP server		Workspace context	Reachable from

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

What Well does with your Lumin connection

Connect

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

Sync

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

Enrich

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

Available

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

Questions Lumin unlocks

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

Ask Well

Ask anything about your Lumin connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Lumin connection…

Connect Lumin in three steps

01
Connect Lumin over its MCP server
Choose Lumin in Well's Connections panel and authorise it through its MCP server at mcp.luminpdf.com over OAuth. Well registers a client via Dynamic Client Registration and walks you through Lumin's consent step, with no keys to paste.
- AuthOAuth (MCP DCR)
- MCP servermcp.luminpdf.com/mcp
02
Make it reachable
The connection puts Lumin within reach of your workspace and its agents. Lumin does not expose financial entities for Well to map today, so there is no invoice, transaction, or account sync to configure; Well will not invent one to fill the step.
- Mappingnone (reach-only)
03
Use it from your workspace
Use the connection to reach Lumin from the same place your agents reach the rest of your stack. If Lumin later exposes structured entities that map onto what Well captures, the data-flow section would reflect the real records rather than placeholder claims.
- Availabilityreachable as soon as connect completes

The OAuth handshake completes in about a minute. This is a reach-and-availability connection, not a data feed, so nothing backfills.

How Lumin stays secure with Well

Lumin connects over its MCP server, with OAuth Dynamic Client Registration handling the credential so Well never holds a Lumin secret. Because no structured financial entity is mapped today, the token simply makes Lumin reachable from your workspace rather than pulling records. The connection is read-only and grants Well nothing it could change in Lumin.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.luminpdf.com/mcp

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

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

Frequently asked questions about Lumin and Well

Choose Lumin in Well's Connections panel and authorise it through its MCP server over OAuth. Well registers a client via Dynamic Client Registration and walks you through Lumin's consent step, with no keys to paste. The connection puts Lumin within reach of your workspace and agents.

Nothing structured, and Well is candid about that. Lumin does not expose financial entities for Well to map, so there is no invoice, transaction, or account sync to set up. The connector exists so Lumin can be reached alongside your other tools; richer structured sync would depend on Lumin exposing the kind of data Well captures, which it does not today.

The connection lets agents in your workspace reach Lumin in the same place they reach the rest of your stack, rather than treating it as a separate silo. It is a reach-and-availability connector, not a data feed: useful for keeping one connected surface, honest about not pulling structured records that are not there.

Only if and when Lumin 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; the connection stays an availability link. If that changes, the data-flow section would reflect the real entities rather than placeholder claims.

Disconnect Lumin in Well and the OAuth token is revoked and the MCP reach ends immediately. Because nothing structured was being synced, there are no workspace records to retain or purge from the connection. It simply removes Lumin from the set of tools your agents can reach through Well.