Integrations · Research

Connect BioRender to Well

Connect BioRender to Well through its MCP server over OAuth. No financial-entity sync is configured for BioRender today; the connection lets your agents reach BioRender alongside the rest of your research workspace.

Connect BioRenderSee what Well does

What Well pulls from BioRender

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

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

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

What Well does with your BioRender connection

Connect

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

Sync

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

Enrich

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

Available

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

Questions BioRender unlocks

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

Ask Well

Ask anything about your BioRender connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your BioRender connection…

Connect BioRender in three steps

01
Connect BioRender over its MCP server
Choose BioRender in Well's Connections panel and authorise it through its MCP server at mcp.services.biorender.com over OAuth. Well registers a client via Dynamic Client Registration and walks you through BioRender's consent step, with no keys to paste.
- AuthOAuth (MCP DCR)
- MCP servermcp.services.biorender.com/mcp
02
Make it reachable
The connection puts BioRender within reach of your workspace and its agents. BioRender 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 BioRender from the same place your agents reach the rest of your stack. If BioRender 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 BioRender stays secure with Well

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

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.services.biorender.com/mcp

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

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

Frequently asked questions about BioRender and Well

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

Nothing structured, and Well is candid about that. BioRender 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 BioRender can be reached alongside your other tools; any richer structured sync would depend on BioRender exposing the kind of data Well captures, which it does not today.

The connection lets agents in your workspace reach BioRender in the same place they reach the rest of your research and finance 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 BioRender 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 and reconciliation sections would reflect the real entities rather than placeholder claims.

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