Skip to content

feat(data-sources): add native Jam MCP provider - #320

Merged
siisee11 merged 2 commits into
mainfrom
codex/native-jam-provider
Jul 21, 2026
Merged

feat(data-sources): add native Jam MCP provider#320
siisee11 merged 2 commits into
mainfrom
codex/native-jam-provider

Conversation

@siisee11

@siisee11 siisee11 commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

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

  • Adds Jam to the native provider registry with provider icons for shared UI and the public provider catalog.
  • Accepts Jam personal access tokens and validates connections against the official Jam MCP endpoint.
  • Exposes approved read-only Jam MCP tools through Source API, including recording analysis, transcripts, logs, network requests, events, metadata, and workspace listings.
  • Excludes comment creation, Jam updates, and binary screenshot retrieval.

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

  • Registers jam as a connectable, testable, analysis-enabled Source API provider.
  • Adds a typed JamCredentials schema for workspace personal access tokens.
  • Adds a Streamable HTTP MCP client for https://mcp.jam.dev/mcp with bearer authentication, timeout handling, and credential-safe errors.
  • Discovers the server tool schemas dynamically while filtering them through a fixed read-only allowlist.
  • Maps structured Source API field patches to MCP tool arguments and normalizes MCP responses as JSON.
  • Adds connection, credential, registry, adapter, shared provider-icon, and landing-icon coverage.

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 format
  • bun run typecheck in packages/db, packages/server, packages/ui, and apps/landing
  • bunx vitest run src/credentials.test.ts src/jam-credentials.test.ts src/schema/data-sources.test.ts in packages/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.ts in packages/server
  • bunx vitest run src/data-sources/provider-icons.test.tsx in packages/ui
  • bunx vitest run src/shared/icons/brands.test.tsx in apps/landing

Video / Screenshot (Optional)

  • N/A

@siisee11
siisee11 enabled auto-merge (squash) July 21, 2026 01:26
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 21, 2026

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

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

@siisee11
siisee11 merged commit 16cb822 into main Jul 21, 2026
8 checks passed
@siisee11
siisee11 deleted the codex/native-jam-provider branch July 21, 2026 02:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant