Integrations · Content

Connect Guru to Well

Name: Guru entities in Well
Creator: Well

Index Guru card, collection, and verifier so your agents can search across them alongside the rest of your workspace.

What Well pulls from Guru

Guru feeds card, collection, verifier into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Guru’s access.

From Guru	In Well	Relation
Card	Indexed record	Becomes
Collection	Workspace context	Groups under
Verifier	Team member	Resolves to

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

What Well does with your Guru connection

Connect

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

Sync

Well brings card, collection, and verifier in from Guru 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 Guru entity into indexed record, workspace context, and team member, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Guru lands in the workspace as indexed record, workspace context, and team member you can search, chart, and automate.

Questions Guru unlocks

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

Ask Well

Ask anything about your Guru connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Guru connection…

Connect Guru in three steps

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

How Guru stays secure with Well

Well connects to Guru's MCP server (mcp.api.getguru.com/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Guru secret. Tokens are scoped to the card, collection, and verifier Guru exposes and refreshed server-side. Reads only, Well cannot modify or delete Guru records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.api.getguru.com/mcp

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

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

Frequently asked questions about Guru and Well

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

Well brings in card, collection, and verifier from Guru and reshapes each entity into your workspace: card becomes indexed record; collection becomes workspace context. Every record arrives with the source identifier preserved, so Guru stays the source of truth while Well lets you query the data alongside the rest of your stack.

Cards, pages, and assets published in Guru are indexed as searchable workspace entities. Conversation queries match across Guru content and your other tools, returning the Guru link, the author, and any linked workspace context (the customer the card targets, the workflow it supports).

Well watches for updates to cards and applies them on the next sync, preserving the original workspace identifier so anything downstream (records tables, conversation history, agent runs) keeps pointing at the right indexed record. Edits flow in incrementally; nothing is duplicated, and the Guru source identifier is retained on every revision.

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

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

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