Integrations · Productivity

Connect Quant to Well

Name: Quant entities in Well
Creator: Well

Bring Quant strategy outputs, position records, and backtest results into Well, joined to the assets and counterparties you track.

Connect QuantSee what Well does

What Well pulls from Quant

Quant feeds campaign, metric, owner into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Quant’s access.

From Quant	In Well	Relation
Campaign	Performance record	Becomes
Metric	Dashboard signal	Feeds
Owner	Team member	Resolves to

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

What Well does with your Quant connection

Connect

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

Sync

Well brings campaign, metric, and owner in from Quant 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 Quant entity into performance record, dashboard signal, and team member, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Quant lands in the workspace as performance record, dashboard signal, and team member you can search, chart, and automate.

Questions Quant unlocks

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

Ask Well

Ask anything about your Quant connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Quant connection…

Connect Quant in three steps

01
Authorise Quant via MCP
From Well's Connections panel, search for Quant and click Connect. Well discovers Quant's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Quant's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP serverai.quanti.io/mcp
02
Map your entities
Well's MCP client discovers campaign, metric, and owner from Quant that Quant'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 Quant records. Because Quant 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 Quant records happens in the background.

How Quant stays secure with Well

Well connects to Quant's MCP server (ai.quanti.io/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Quant secret. Tokens are scoped to the campaign, metric, and owner Quant exposes and refreshed server-side. Reads only, Well cannot modify or delete Quant records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsai.quanti.io/mcp

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

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

Frequently asked questions about Quant and Well

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

Well brings in campaign, metric, and owner from Quant and reshapes each entity into your workspace: campaign becomes performance record; metric becomes dashboard signal. Every record arrives with the source identifier preserved, so Quant stays the source of truth while Well lets you query the data alongside the rest of your stack.

Each Quant strategy, position, and backtest result is linked to the matching assets or counterparties in your workspace. Ask "show me current PnL by strategy across our positions" and Well returns the strategy-by-asset roll-up with backtest history and live performance side by side.

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

Well combines live Quant events with periodic reconciliation reads of campaign, metric, and owner. New rows appear within seconds when Quant pushes them; periodic reads catch anything a push missed. The first connect backfills history from Quant in the background.

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

Quant 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.