Integrations · Development

Connect Stytch to Well

Name: Stytch entities in Well
Creator: Well

Link Stytch user, session, and organization to the customer and revenue context they affect.

What Well pulls from Stytch

Stytch feeds user, session, organization into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Stytch’s access.

From Stytch	In Well	Relation
User	Person	Resolves to
Session	Audit entry	Captures as
Organization	Customer	Groups under

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

What Well does with your Stytch connection

Connect

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

Sync

Well brings user, session, and organization in from Stytch 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 Stytch entity into person, audit entry, and customer, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Stytch lands in the workspace as person, audit entry, and customer you can search, chart, and automate.

Questions Stytch unlocks

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

Ask Well

Ask anything about your Stytch connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Stytch connection…

Connect Stytch in three steps

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

How Stytch stays secure with Well

Well connects to Stytch's MCP server (mcp.stytch.dev/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Stytch secret. Tokens are scoped to the user, session, and organization Stytch exposes and refreshed server-side. Reads only, Well cannot modify or delete Stytch records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.stytch.dev/mcp

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

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

Frequently asked questions about Stytch and Well

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

Well brings in user, session, and organization from Stytch and reshapes each entity into your workspace: user becomes person; session becomes audit entry. Every record arrives with the source identifier preserved, so Stytch stays the source of truth while Well lets you query the data alongside the rest of your stack.

Well links Stytch activity (issues, commits, deploys, runs) to the customer accounts in your CRM that originated each request. A bug report from a top-revenue customer shows that revenue context inline; a deploy mentions the customer-facing features that just shipped.

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

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

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

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