feat(data-sources): add native Jam MCP provider - #320
Merged
Conversation
siisee11
enabled auto-merge (squash)
July 21, 2026 01:26
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
onequery-landing | d774c41 | Commit Preview URL Branch Preview URL |
Jul 21 2026, 02:22 AM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One-Line Summary
Velen-compatible consumers can connect Jam as a native data source and analyze recordings, transcripts, console logs, network requests, metadata, and user events through Jam MCP.
User-Facing Changes
Why This Changed
Jam recordings previously had no native provider contract, credential schema, connection test, or Source API adapter. Velen therefore could not discover Jam capabilities or safely execute recording and log analysis through its normal data-source workflow.
How It Changed
jamas a connectable, testable, analysis-enabled Source API provider.JamCredentialsschema for workspace personal access tokens.https://mcp.jam.dev/mcpwith bearer authentication, timeout handling, and credential-safe errors.Extra Context / Decisions (Optional)
The adapter deliberately omits write tools and
getScreenshot. Screenshot results are binary and do not fit the current Source API agent serialization path.Verification
bun run formatbun run typecheckinpackages/db,packages/server,packages/ui, andapps/landingbunx vitest run src/credentials.test.ts src/jam-credentials.test.ts src/schema/data-sources.test.tsinpackages/db(220 tests)bunx vitest run src/source-api/adapters/jam.test.ts src/services/testers/jam-tester.test.ts src/source-api/registry.test.tsinpackages/serverbunx vitest run src/data-sources/provider-icons.test.tsxinpackages/uibunx vitest run src/shared/icons/brands.test.tsxinapps/landingVideo / Screenshot (Optional)