Integrations · Development

Connect DocFork to Well

Add DocFork to Well over its MCP server to keep its documentation within reach of your agents and your workspace. DocFork exposes no structured financial entity for Well to map today, so connecting is about reach across one context, not a synced records feed.

Connect DocForkSee what Well does

What Well pulls from DocFork

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

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

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

What Well does with your DocFork connection

Connect

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

Sync

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

Enrich

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

Available

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

Questions DocFork unlocks

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

Ask Well

Ask anything about your DocFork connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your DocFork connection…

Connect DocFork in three steps

01
Connect DocFork over its MCP server
Pick DocFork in Well's Connections panel and authorise it through its MCP server at mcp.docfork.com over OAuth. Well registers a client via Dynamic Client Registration and walks you through DocFork's consent step, with no keys to paste.
- AuthOAuth (MCP DCR)
- MCP servermcp.docfork.com
02
Make it reachable
The connection puts DocFork within reach of your workspace and its agents. DocFork exposes no structured financial entity for Well to map today, so there is no invoice, transaction, or account sync to configure.
- Mappingnone (reach-only)
03
Use it from your workspace
Use the connection to let an agent reach the documentation DocFork holds from the same place it reaches the rest of your stack. If DocFork 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

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

How DocFork stays secure with Well

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

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.docfork.com

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

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

Frequently asked questions about DocFork and Well

It puts DocFork within reach of the agents working in your workspace. You authorise DocFork through its MCP server at mcp.docfork.com over OAuth, Well registers a client via Dynamic Client Registration, and the documentation DocFork serves becomes reachable from the same place as the rest of your stack. There are no keys to paste in the connect step.

No, and the page says so plainly. DocFork exposes no supported target model for Well to map into an invoice, transaction, or account, so there is no structured sync to configure. The connection is an availability link: it lets an agent reach the documents DocFork holds while it works, rather than turning them into workspace records.

Because reach across one context still matters. An agent can pull the documentation DocFork serves from the same workspace it reaches your other tools, instead of treating it as a separate destination to go look something up in. It is a reach-and-availability connector, honest about not pulling structured records that DocFork does not expose.

Only if DocFork starts exposing structured entities through its MCP server that map onto what Well captures. Until that happens, Well will not fabricate a synced record to pad the page. If it changes, the data-flow and reconciliation sections would show the real entities; today the connection's value is documentation reach for your agents.

Disconnect DocFork in Well and the OAuth token is revoked and the MCP reach ends at once. Since nothing structured was being synced, there are no workspace records to keep or purge. Disconnecting simply removes DocFork from the set of tools your agents can reach through Well.