Integrations · Productivity

Connect Linear to Well

Name: Linear entities in Well
Creator: Well

Index Linear issue, project, assignee, and customer label so questions about work item and workspace context answer themselves in conversation.

Connect LinearSee what Well does

What Well pulls from Linear

Linear feeds issue, project, assignee into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Linear’s access.

From Linear	In Well	Relation
Issue	Work item	Indexes as
Project	Workspace context	Groups under
Assignee	Team member	Resolves to
Customer label	Company	Links to

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

What Well does with your Linear connection

Connect

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

Sync

Well brings issue, project, and assignee in from Linear 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 Linear entity into work item, 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 Linear lands in the workspace as work item, workspace context, and team member you can search, chart, and automate.

Questions Linear unlocks

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

Ask Well

Ask anything about your Linear connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Linear connection…

Connect Linear in three steps

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

How Linear stays secure with Well

Well connects to Linear's MCP server (mcp.linear.app/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Linear secret. Tokens are scoped to the issue, project, assignee, and customer label Linear exposes and refreshed server-side. Reads only, Well cannot modify or delete Linear records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.linear.app/mcp

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

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

Frequently asked questions about Linear and Well

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

Well brings in issue, project, assignee, and customer label from Linear and reshapes each entity into your workspace: issue becomes work item; project becomes workspace context. Every record arrives with the source identifier preserved, so Linear stays the source of truth while Well lets you query the data alongside the rest of your stack.

Every Linear record is scanned for references to companies, contacts, and deal names in your workspace. Matches are surfaced inline on each entity's workspace page: a customer's profile shows the Linear tasks and threads that mention them, ranked by recency and reach.

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

Well combines live Linear events with periodic reconciliation reads of issue, project, assignee, and customer label. New rows appear within seconds when Linear pushes them; periodic reads catch anything a push missed. The first connect backfills history from Linear in the background.

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

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