Integrations · Research

Connect Synapse.org to Well

Name: Synapse.org entities in Well
Creator: Well

Organise Synapse.org dataset, citation, author, and publication alongside the rest of your research workflow, with citations preserved.

Connect Synapse.orgSee what Well does

What Well pulls from Synapse.org

Synapse.org feeds dataset, citation, author into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Synapse.org’s access.

From Synapse.org	In Well	Relation
Dataset	Workspace dataset	Materializes as
Citation	Research reference	Indexes as
Author	Contact	Resolves to
Publication	Workspace document	Indexes as

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: Synapse.org → Well

What Well does with your Synapse.org connection

Connect

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

Sync

Well brings dataset, citation, and author in from Synapse.org 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 Synapse.org entity into workspace dataset, research reference, and contact, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Synapse.org lands in the workspace as workspace dataset, research reference, and contact you can search, chart, and automate.

Questions Synapse.org unlocks

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

Ask Well

Ask anything about your Synapse.org connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Synapse.org connection…

Connect Synapse.org in three steps

01
Authorise Synapse.org via MCP
From Well's Connections panel, search for Synapse.org and click Connect. Well discovers Synapse.org's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Synapse.org's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.synapse.org/mcp
02
Map your entities
Well's MCP client discovers dataset, citation, author, and publication from Synapse.org that Synapse.org's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.
- Mappingpreconfigured by Well
03
Use the data
Ask questions in conversation, build records tables, or let agents act on Synapse.org records. Because Synapse.org ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.
- First syncstarts as soon as connect completes

MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical Synapse.org records happens in the background.

How Synapse.org stays secure with Well

Well connects to Synapse.org's MCP server (mcp.synapse.org/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Synapse.org secret. Tokens are scoped to the dataset, citation, author, and publication Synapse.org exposes and refreshed server-side. Reads only, Well cannot modify or delete Synapse.org records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.synapse.org/mcp

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

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

Frequently asked questions about Synapse.org and Well

From Well, open Connections, find Synapse.org, and click Connect. Well discovers the OAuth metadata at mcp.synapse.org/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Synapse.org's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

Well brings in dataset, citation, author, and publication from Synapse.org and reshapes each entity into your workspace: dataset becomes workspace dataset; citation becomes research reference. Every record arrives with the source identifier preserved, so Synapse.org stays the source of truth while Well lets you query the data alongside the rest of your stack.

Citations, briefs, and findings from Synapse.org are indexed alongside your other workspace context. Questions like "what does Synapse.org say about our top three competitors" or "which sources cover our most recent product launch" return ranked answers with citation links preserved, so source-attribution is one click away.

Every workspace workspace dataset built from Synapse.org carries the source dataset identifier plus a deep link back to the original record. From a workspace page, one click takes you to the Synapse.org record; from Synapse.org, the workspace identifier travels back so you can search either direction. The link survives every subsequent enrichment Well runs.

Well combines live Synapse.org events with periodic reconciliation reads of dataset, citation, author, and publication. New rows appear within seconds when Synapse.org pushes them; periodic reads catch anything a push missed. The first connect backfills history from Synapse.org in the background.

Open Connections > Synapse.org in Well and click Disconnect. Well calls Synapse.org's token revocation endpoint and stops calling Synapse.org immediately on its side; provider-side propagation to Synapse.org's admin panel varies by provider. The dataset, citation, author, and publication Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

Synapse.org records are stored in the region Well operates for your workspace. Specific region details and the steps to change region are available from Support. See /privacy for the current data-handling policy.

Ready to connect Synapse.org?

Connect once. Every dataset, citation, author from Synapse.org becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.

Connect Synapse.orgTalk to us