Integrations · Research

Connect Owkin to Well

Connect Owkin to Well over its MCP server and read its research data against the organisations you track. Owkin maps to the company entity today, so a covered organisation resolves to a workspace company and finer records are not yet structured.

Connect OwkinSee what Well does

What Well pulls from Owkin

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

From Owkin		In Well	Relation
Research organisation		Company	Resolves to

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

What Well does with your Owkin connection

Connect

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

Sync

Well brings research organisation in from Owkin on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each Owkin entity into company, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Owkin lands in the workspace as company you can search, chart, and automate.

Questions Owkin unlocks

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

Ask Well

Ask anything about your Owkin connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Owkin connection…

Connect Owkin in three steps

01
Authorise Owkin over its MCP server
Open Owkin in Well's Connections panel and begin. Well discovers the OAuth metadata at the Owkin MCP server on mcp.k.owkin.com, registers a client through Dynamic Client Registration, and hands you to Owkin to approve the read scopes, with no key to copy across.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.k.owkin.com/mcp
02
Map your entities
Well reads the research data Owkin exposes and maps each covered organisation to the workspace company it represents through Well's data-views layer. People, invoices, and transactions are not mapped today, so the structured anchor is the company.
- Mappingpreconfigured by Well
03
Use the data
From there, ask what Owkin holds on a tracked organisation in conversation, or let an agent join research signal to the company it affects. Owkin is an INPUT connector, so the read runs one way and nothing is written back.
- First syncstarts as soon as connect completes

Connecting takes about a minute. Current data is read on connect and the longer history backfills in the background while you work.

How Owkin stays secure with Well

Well reaches Owkin through its MCP server at mcp.k.owkin.com over the Model Context Protocol, and OAuth Dynamic Client Registration keeps the Owkin credential with Owkin rather than with Well. The grant is scoped to the research data Owkin exposes and refreshes server-side. Every call is a read anchored on the company entity; Well cannot create or change a record in Owkin.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.k.owkin.com/mcp

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

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

Frequently asked questions about Owkin and Well

Choose Owkin in Well's Connections panel to start. Well discovers the OAuth metadata at the Owkin MCP server on mcp.k.owkin.com, registers through Dynamic Client Registration, and routes you to approve the read scopes on Owkin's side. Nothing to paste, and the consent step keeps the choice of what Well may read with you.

The organisation, and the page is precise about that. Owkin maps to the company entity, so a research organisation it covers resolves to a workspace company. The research and discovery data Owkin holds reads across the connection against that company; people, invoices, and transactions are not mapped today, so the structured join is at the organisation level rather than a billing record.

Because the company entity is the anchor. An organisation Owkin covers resolves to the matching company in your workspace, so the research signal Well reads sits against the same record as that company's deals and activity. A question about a tracked organisation can then draw on Owkin's data from the same place that already holds the rest of its context.

Yes, joined at the company level. Once the connection is live an agent can pull what Owkin holds on an organisation you track and answer from your workspace rather than a separate portal. The read is one-way and anchored on the company, so the answer carries the organisation it belongs to even though finer entities are not structured today.

Well reads the organisation-level research data through the Owkin MCP connection and folds fresh signal in as it is read, with the first connect pulling the available history in the background. Owkin stays the system of record for the research; Well keeps a queryable copy so the company-level picture sits next to the rest of your workspace.

Disconnect Owkin in Well and reads stop at once and the token is released; because the connection only ever read, nothing needs reversing on Owkin's side. The company-level research already brought across stays in your workspace for reference, and Support can purge it if a policy requires.