Integrations · Productivity

Connect Atlassian to Well

Name: Atlassian entities in Well
Creator: Well

Index Atlassian issue, epic, assignee, and comment so questions about work item and project context answer themselves in conversation.

Connect AtlassianSee what Well does

What Well pulls from Atlassian

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

From Atlassian	In Well	Relation
Issue	Work item	Indexes as
Epic	Project context	Groups under
Assignee	Team member	Resolves to
Comment	Audit entry	Appends to

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

What Well does with your Atlassian connection

Connect

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

Sync

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

Questions Atlassian unlocks

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

Ask Well

Ask anything about your Atlassian connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Atlassian connection…

Connect Atlassian in three steps

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

How Atlassian stays secure with Well

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

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.atlassian.com/v1/mcp

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

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

Frequently asked questions about Atlassian and Well

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

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

Each Atlassian item carries its assignee, which Well resolves into a workspace team member entity. Asking "who on the team owns Globex in Atlassian right now" returns the assigned people across active Atlassian items, joined to their workspace identity, so you see ownership across tools in one query.

Yes. Atlassian comments are indexed in your workspace as audit entry, so questions like "show me last week's comments from Atlassian" return them with the original Atlassian link, the workspace context, and any related records (counterparty, period, attached document) joined inline.

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

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

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