Connect Scholar Gateway to Well
Organise Scholar Gateway publication, citation, and author alongside the rest of your research workflow, with citations preserved.
What Well pulls from Scholar Gateway
Scholar Gateway feeds publication, citation, author into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Scholar Gateway’s access.
| From Scholar Gateway | In Well | Relation | |
|---|---|---|---|
| Publication | Research entity | Becomes | |
| Citation | Graph edge | Links to | |
| Author | Team member | Resolves to |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- Scholar Gateway → Well
What Well does with your Scholar Gateway connection
Connect
Connect Scholar Gateway over OAuth (MCP DCR): Well registers a client through Scholar Gateway's OAuth Dynamic Client Registration and you approve on Scholar Gateway's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings publication, citation, and author in from Scholar Gateway 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 Scholar Gateway entity into research entity, graph edge, and team member, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from Scholar Gateway lands in the workspace as research entity, graph edge, and team member you can search, chart, and automate.
Questions Scholar Gateway unlocks
Ask in plain language. Well answers from your connected Scholar Gateway connection, resolved against the rest of your stack.
Ask anything about your Scholar Gateway connection
Ask about your Scholar Gateway connection…
Connect Scholar Gateway in three steps
- 01
Authorise Scholar Gateway via MCP
From Well's Connections panel, search for Scholar Gateway and click Connect. Well discovers Scholar Gateway's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Scholar Gateway's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP serverconnector.scholargateway.ai/mcp
- 02
Map your entities
Well's MCP client discovers publication, citation, and author from Scholar Gateway that Scholar Gateway'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 Scholar Gateway records. Because Scholar Gateway 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 Scholar Gateway records happens in the background.
How Scholar Gateway stays secure with Well
Well connects to Scholar Gateway's MCP server (connector.scholargateway.ai/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Scholar Gateway secret. Tokens are scoped to the publication, citation, and author Scholar Gateway exposes and refreshed server-side. Reads only, Well cannot modify or delete Scholar Gateway records.
- granted
Read Scholar Gateway records
Resources the Scholar Gateway MCP server exposes, scoped by your OAuth approval.
- granted
Resolve publication, citation, and author across your stack
Match identifiers in Scholar Gateway against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete Scholar Gateway records
Not granted; Scholar Gateway is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store Scholar Gateway passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Frequently asked questions about Scholar Gateway and Well
From Well, open Connections, find Scholar Gateway, and click Connect. Well discovers the OAuth metadata at connector.scholargateway.ai/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Scholar Gateway's side. No client_id or client_secret to paste; the handshake takes roughly a minute.
Well brings in publication, citation, and author from Scholar Gateway and reshapes each entity into your workspace: publication becomes research entity; citation becomes graph edge. Every record arrives with the source identifier preserved, so Scholar Gateway stays the source of truth while Well lets you query the data alongside the rest of your stack.
Each Scholar Gateway source is linked to the workspace entities it references, customer companies, competitive products, internal projects. Asking "what external research mentions Globex" returns Scholar Gateway citations alongside the internal CRM notes and engineering tickets that overlap, so the external signal sits next to the internal record.
Every workspace research entity built from Scholar Gateway carries the source publication identifier plus a deep link back to the original record. From a workspace page, one click takes you to the Scholar Gateway record; from Scholar Gateway, the workspace identifier travels back so you can search either direction. The link survives every subsequent enrichment Well runs.
Well combines live Scholar Gateway events with periodic reconciliation reads of publication, citation, and author. New rows appear within seconds when Scholar Gateway pushes them; periodic reads catch anything a push missed. The first connect backfills history from Scholar Gateway in the background.
Open Connections > Scholar Gateway in Well and click Disconnect. Well calls Scholar Gateway's token revocation endpoint and stops calling Scholar Gateway immediately on its side; provider-side propagation to Scholar Gateway's admin panel varies by provider. The publication, citation, and author Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.
Scholar Gateway 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.
Pairs well with Scholar Gateway
More in Research
BioRender
Connect BioRender to Well over its MCP server so your agents can reach it, with no structured data sync.
Candid
Connect Candid to Well to sync research data and scientific resources.
Owkin
Connect Owkin to Well to sync research data and scientific resources.
Synapse.org
Connect Synapse.org to Well to sync research data and scientific resources.
Popular cross-category
Ready to connect Scholar Gateway?
Connect once. Every publication, citation, author from Scholar Gateway becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.