Integrations · DevelopmentConnect Jam to Well
Link Jam bug report, recording, and reporter to the customer and revenue context they affect.
What Well pulls from Jam
Jam feeds bug report, recording, reporter into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Jam’s access.
| From Jam | In Well | Relation | |
|---|---|---|---|
| Bug report | Work item | Becomes | |
| Recording | Audit attachment | Preserves as | |
| Reporter | Team member | Resolves to |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- Jam → Well
What Well does with your Jam connection
Connect
Connect Jam over OAuth (MCP DCR): Well registers a client through Jam's OAuth Dynamic Client Registration and you approve on Jam's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings bug report, recording, and reporter in from Jam 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 Jam entity into work item, audit attachment, and team member, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from Jam lands in the workspace as work item, audit attachment, and team member you can search, chart, and automate.
Questions Jam unlocks
Ask in plain language. Well answers from your connected Jam connection, resolved against the rest of your stack.
Ask anything about your Jam connection
Ask about your Jam connection…
Connect Jam in three steps
- 01
Authorise Jam via MCP
From Well's Connections panel, search for Jam and click Connect. Well discovers Jam's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Jam's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.jam.dev/mcp
- 02
Map your entities
Well's MCP client discovers bug report, recording, and reporter from Jam that Jam'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 Jam records. Because Jam 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 Jam records happens in the background.
How Jam stays secure with Well
Well connects to Jam's MCP server (mcp.jam.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 Jam secret. Tokens are scoped to the bug report, recording, and reporter Jam exposes and refreshed server-side. Reads only, Well cannot modify or delete Jam records.
- granted
Read Jam records
Resources the Jam MCP server exposes, scoped by your OAuth approval.
- granted
Resolve bug report, recording, and reporter across your stack
Match identifiers in Jam against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete Jam records
Not granted; Jam is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store Jam passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Frequently asked questions about Jam and Well
From Well, open Connections, find Jam, and click Connect. Well discovers the OAuth metadata at mcp.jam.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 Jam's side. No client_id or client_secret to paste; the handshake takes roughly a minute.
Well brings in bug report, recording, and reporter from Jam and reshapes each entity into your workspace: bug report becomes work item; recording becomes audit attachment. Every record arrives with the source identifier preserved, so Jam stays the source of truth while Well lets you query the data alongside the rest of your stack.
Deploys and runs in Jam carry their commit refs, which Well joins back to the workspace entities (features, projects) those commits relate to. Asking "what changed for our enterprise tier this week" returns a ranked list of deploys with the customer-facing surface they touched.
Yes. Jam reporters are indexed in your workspace as team member, so questions like "show me last week's reporters from Jam" return them with the original Jam link, the workspace context, and any related records (counterparty, period, attached document) joined inline.
Well combines live Jam events with periodic reconciliation reads of bug report, recording, and reporter. New rows appear within seconds when Jam pushes them; periodic reads catch anything a push missed. The first connect backfills history from Jam in the background.
Open Connections > Jam in Well and click Disconnect. Well calls Jam's token revocation endpoint and stops calling Jam immediately on its side; provider-side propagation to Jam's admin panel varies by provider. The bug report, recording, and reporter Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.
Jam 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.
Pairs well with Jam
More in Development
Cloudflare
Connect Cloudflare to Well to sync development tools and infrastructure data.
Context7
Connect Context7 to Well over its MCP server so your agents can reach it, with no structured data sync.
DocFork
Connect DocFork to Well over its MCP server so your agents can reach it, with no structured data sync.
GitLab
Connect GitLab to Well to sync development tools and infrastructure data.
Popular cross-category
Ready to connect Jam?
Connect once. Every bug report, recording, reporter from Jam becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.