Integrations · ResearchConnect Candid to Well
Read Candid's nonprofit and grant research into Well over its MCP server. Foundations and grant records resolve to the companies and people they involve, so philanthropic data is queryable beside the rest of your workspace.
What Well pulls from Candid
Candid feeds nonprofit record, grant, organization into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Candid’s access.
| From Candid | In Well | Relation | |
|---|---|---|---|
| Nonprofit record | Research entity | Becomes | |
| Grant | Funding signal | Feeds | |
| Organization | Entity | Resolves to |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- Candid → Well
What Well does with your Candid connection
Connect
Connect Candid over OAuth (MCP DCR): Well registers a client through Candid's OAuth Dynamic Client Registration and you approve on Candid's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings nonprofit record, grant, and organization in from Candid 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 Candid entity into research entity, funding signal, and entity, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from Candid lands in the workspace as research entity, funding signal, and entity you can search, chart, and automate.
Questions Candid unlocks
Ask in plain language. Well answers from your connected Candid connection, resolved against the rest of your stack.
Ask anything about your Candid connection
Ask about your Candid connection…
Connect Candid in three steps
- 01
Authorise Candid through its MCP server
Select Candid in Well's Connections panel to begin. Well fetches the OAuth metadata from the Candid MCP server at mcp.candid.org, registers via Dynamic Client Registration, and routes you to Candid to approve the read scopes. No keys to manage; you decide on Candid's screen what Well may read.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.candid.org/mcp
- 02
Map your entities
Well reads nonprofit profiles, Form 990 filings, and grant records, resolving each foundation to a company and the people behind it to person records through Well's data-views layer so funding signal lands against the right entity.
- Mappingpreconfigured by Well
- 03
Use the data
Then ask which foundations fund a sector in conversation, surface open grants by deadline, or let an agent match grants to your eligibility. Candid 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. Reference profiles are read on connect and the longer grant history backfills in the background.
How Candid stays secure with Well
Well talks to Candid through its MCP server at mcp.candid.org using the Model Context Protocol, and OAuth Dynamic Client Registration means the Candid credential is never held by Well. The granted token is scoped to the nonprofit profiles, filings, and grant records Candid exposes, and it refreshes server-side. The connection reads the research; it cannot create or change a record in Candid.
- granted
Read Candid records
Resources the Candid MCP server exposes, scoped by your OAuth approval.
- granted
Resolve nonprofit record, grant, and organization across your stack
Match identifiers in Candid against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete Candid records
Not granted; Candid is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store Candid passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Frequently asked questions about Candid and Well
Select Candid in Well's Connections panel to start. Well fetches the OAuth metadata from the Candid MCP server at mcp.candid.org, registers through Dynamic Client Registration, and sends you to Candid to approve the read scopes. There are no API keys to manage, and you decide on Candid's screen exactly what Well may read.
Candid holds nonprofit profiles, Form 990 filings, and grant records, so Well reads the organisations, their filings, and the grants tied to them across the connection. The read is one-way: Well pulls the philanthropic research in and never edits a profile or filing back in Candid. The data sits in your workspace context beside the rest of your records.
Candid maps to the company and people entities, so a foundation resolves to a workspace company and the people behind it resolve to person records. Grant figures read over the connection feed funding signal against that company, which lets a question about which foundations funded an organisation answer from the same place that holds the rest of its profile.
Yes. Because grant records arrive as workspace data joined to the funders behind them, an agent can rank open grants by deadline or surface the foundations whose giving fits your sector and size, and answer from your workspace. Each grant keeps its funder and historical award size, so the answer carries the context to act on it.
Well reads nonprofit profiles, filings, and grant records through the Candid MCP connection and folds fresh records in as they are read, with the first connect pulling the available history in the background. Candid stays the system of record for the research; Well keeps a queryable copy so philanthropic data sits next to the rest of your workspace.
Disconnect Candid in Well and Well stops reading through the MCP server immediately and releases its token. Candid is read-only in Well, so no record needs reversing on its side. The profiles, filings, and grant records already read stay in your workspace for reporting; ask Support to purge them if your compliance flow requires it.
Pairs well with Candid
More in Research
BioRender
Connect BioRender to Well over its MCP server so your agents can reach it, with no structured data sync.
Owkin
Connect Owkin to Well to sync research data and scientific resources.
Scholar Gateway
Connect Scholar Gateway 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 Candid?
Connect once. Every nonprofit record, grant, organization from Candid becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.