Integrations · Development

Connect Context7 to Well

Connect Context7 to Well over its MCP server so your agents can reach up-to-date library documentation from the same workspace they reach everything else. Context7 exposes no structured financial entity for Well to map today, so the connection is about reach, not a records sync.

Connect Context7See what Well does

What Well pulls from Context7

Context7 feeds Context7 MCP server into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Context7’s access.

From Context7		In Well	Relation
Context7 MCP server		Workspace context	Reachable from

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

What Well does with your Context7 connection

Connect

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

Sync

Connecting Context7 makes it reachable from your workspace; Context7 exposes no structured records for Well to sync into the data model today.

Enrich

With no records to ingest, Context7 adds reach without enrichment; entity resolution and categorisation run for connectors that bring structured data in.

Available

Context7 is reachable from conversation and agents in your workspace; once it exposes structured records they land alongside the rest of your connected tools.

Questions Context7 unlocks

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

Ask Well

Ask anything about your Context7 connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Context7 connection…

Connect Context7 in three steps

01
Connect Context7 over its MCP server
Choose Context7 in Well's Connections panel and authorise it through its MCP server at mcp.context7.com over OAuth. Well registers a client via Dynamic Client Registration and walks you through Context7's consent step, with no keys to paste.
- AuthOAuth (MCP DCR)
- MCP servermcp.context7.com/mcp
02
Make it reachable
The connection puts Context7 within reach of your workspace and its agents. Context7 exposes no structured financial entity for Well to map today, so there is no invoice, transaction, or account sync to set up; Well will not invent one to fill the step.
- Mappingnone (reach-only)
03
Use it from your workspace
Use the connection to let an agent pull current library documentation from Context7 in the same place it reaches the rest of your stack. If Context7 later exposes structured entities that map onto what Well captures, the data-flow section would reflect the real records.
- Availabilityreachable as soon as connect completes

The OAuth handshake completes in about a minute. This is a reach-and-availability connection, not a records feed, so nothing backfills.

How Context7 stays secure with Well

Context7 connects over its MCP server at mcp.context7.com, with OAuth Dynamic Client Registration handling the credential so Well never holds a Context7 secret. Because no structured financial entity is mapped today, the token simply makes Context7 reachable from your workspace rather than pulling records. The connection is read-only and grants Well nothing it could change in Context7.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.context7.com/mcp

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

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

Frequently asked questions about Context7 and Well

Choose Context7 in Well's Connections panel and authorise it through its MCP server at mcp.context7.com over OAuth. Well registers a client via Dynamic Client Registration and walks you through the consent step on Context7's side, with no keys to paste. The connection puts Context7 within reach of your workspace and its agents.

No structured financial entity, and the page is candid about that. Context7 serves up-to-date library and framework documentation, but it exposes no supported target model for Well to turn into an invoice, transaction, or account. So there is no records table to configure; the connection is about reach, letting your agents pull the documentation Context7 holds rather than feeding a sync.

It lets an agent in your workspace pull current documentation for a library straight from Context7 while it works, in the same place it reaches the rest of your stack, instead of treating docs as a separate lookup. This is a reach-and-availability connection: useful for keeping one connected surface, honest about not pulling structured records that are not there.

Only if and when Context7 exposes structured entities through its MCP server that map onto what Well captures. Until then Well will not invent a synced record to make the page look fuller. If that changes, the data-flow section would reflect the real entities rather than placeholder claims; for now the value is live documentation reach.

Disconnect Context7 in Well and the OAuth token is revoked and the MCP reach ends immediately. Because nothing structured was being synced, there are no workspace records to retain or purge from the connection. It simply removes Context7 from the set of tools your agents can reach through Well.