Integrations · Market dataConnect Chronograph to Well
Bring Chronograph portfolio metrics, NAVs, and fund cashflows into Well, joined to the funds and portfolio companies you track.
What Well pulls from Chronograph
Chronograph feeds portfolio metric, company, report into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Chronograph’s access.
| From Chronograph | In Well | Relation | |
|---|---|---|---|
| Portfolio metric | Performance record | Becomes | |
| Company | Investment | Resolves to | |
| Report | Audit entry | Captures as |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- Chronograph → Well
What Well does with your Chronograph connection
Connect
Connect Chronograph over OAuth (MCP DCR): Well registers a client through Chronograph's OAuth Dynamic Client Registration and you approve on Chronograph's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings portfolio metric, company, and report in from Chronograph 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 Chronograph entity into performance record, investment, and audit entry, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from Chronograph lands in the workspace as performance record, investment, and audit entry you can search, chart, and automate.
Questions Chronograph unlocks
Ask in plain language. Well answers from your connected Chronograph connection, resolved against the rest of your stack.
Ask anything about your Chronograph connection
Ask about your Chronograph connection…
Connect Chronograph in three steps
- 01
Authorise Chronograph via MCP
From Well's Connections panel, search for Chronograph and click Connect. Well discovers Chronograph's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Chronograph's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP serverai.chronograph.pe/mcp
- 02
Map your entities
Well's MCP client discovers portfolio metric, company, and report from Chronograph that Chronograph'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 Chronograph records. Because Chronograph 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 Chronograph records happens in the background.
How Chronograph stays secure with Well
Well connects to Chronograph's MCP server (ai.chronograph.pe/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Chronograph secret. Tokens are scoped to the portfolio metric, company, and report Chronograph exposes and refreshed server-side. Reads only, Well cannot modify or delete Chronograph records.
- granted
Read Chronograph records
Resources the Chronograph MCP server exposes, scoped by your OAuth approval.
- granted
Resolve portfolio metric, company, and report across your stack
Match identifiers in Chronograph against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete Chronograph records
Not granted; Chronograph is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store Chronograph passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Frequently asked questions about Chronograph and Well
From Well, open Connections, find Chronograph, and click Connect. Well discovers the OAuth metadata at ai.chronograph.pe/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Chronograph's side. No client_id or client_secret to paste; the handshake takes roughly a minute.
Well brings in portfolio metric, company, and report from Chronograph and reshapes each entity into your workspace: portfolio metric becomes performance record; company becomes investment. Every record arrives with the source identifier preserved, so Chronograph stays the source of truth while Well lets you query the data alongside the rest of your stack.
Each Chronograph NAV, cashflow, and portfolio-company metric is linked to the matching fund or company in your workspace. Ask "show me the latest NAV on the Globex fund" and Well returns the time series with peer benchmarks and contribution attribution.
Every workspace performance record built from Chronograph carries the source portfolio metric identifier plus a deep link back to the original record. From a workspace page, one click takes you to the Chronograph record; from Chronograph, the workspace identifier travels back so you can search either direction. The link survives every subsequent enrichment Well runs.
Well combines live Chronograph events with periodic reconciliation reads of portfolio metric, company, and report. New rows appear within seconds when Chronograph pushes them; periodic reads catch anything a push missed. The first connect backfills history from Chronograph in the background.
Open Connections > Chronograph in Well and click Disconnect. Well calls Chronograph's token revocation endpoint and stops calling Chronograph immediately on its side; provider-side propagation to Chronograph's admin panel varies by provider. The portfolio metric, company, and report Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.
Chronograph 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 Chronograph
More in Market data
Popular cross-category
Ready to connect Chronograph?
Connect once. Every portfolio metric, company, report from Chronograph becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.