Connect Jam to Andromity with the Jam MCP server

Jam hosts an official MCP server at https://mcp.jam.dev/mcp. With it, Andromity can open a Jam bug report from its link, read the console logs, network requests and user events captured with it, and use that context to find and fix the bug in your repository.

Sign-in is a browser flow. You sign in to Jam and allow access to your workspace.

What the agent can do with Jam

• Read a Jam's details, metadata, console logs, network requests and user events (getDetails, getMetadata, getConsoleLogs, getNetworkRequests, getUserEvents).
• Read screenshots, video frames, the video transcript and chapters of a Jam (getScreenshots, getFrames, getVideoTranscript, getVideoChapters).
• Search Jams and list workspace members and folders (searchJams, listMembers, listFolders).
• Comment on a Jam, edit or delete comments, and add or remove reactions (createComment, editComment, deleteComment, addReaction, removeReaction).
• Update a Jam, and create, update or delete folders (updateJam, createFolder, updateFolder, deleteFolder).
• Manage Jam Recording Links (listRecordingLinks, createRecordingLink, updateRecordingLink and related tools).

Example prompts

Ask for the work in plain language. Naming the server helps, for example “use the Jam MCP server”.

• Read this Jam link, check the console errors and failed network requests, find the cause in this repo and fix it.
• Look at the user events in this Jam, reproduce the steps as a failing test, then make it pass.
• Search Jams for reports about the checkout page and tell me which ones this branch could fix.
• Fix the bug in this Jam, then add a comment on it that says what changed.

Connect Jam

1. In Jam, record the bug with the Jam Chrome extension and copy the Jam link.
2. In VS Code, open Andromity Hub → MCP Servers → Discover. In the terminal app, open /settings → MCP → + Connect an app. Find Jam and select Connect.
3. Sign in to Jam in your browser and allow access to your workspace. Andromity saves Jam to ~/.andromity/mcp.json and connects it.
4. Paste a Jam link into the chat.

See Connect an app for how Andromity stores connectors and tokens.

Access and safety

• Jam says MCP mirrors your existing Jam permissions. The agent can see only what you can see in the Jam web or mobile app.
• Jam admins manage access through member roles or SSO in Settings. You can review and revoke connected tools at Settings → MCP in Jam.
• deleteJam and deleteFolder are permanent, and deleting a folder deletes every Jam inside it. Andromity's SAFE mode asks before every tool call; TRUST mode asks for tools whose names contain delete, create or update.

In an untrusted folder, MCP servers don’t start at all. Read workspace trust and permission modes for the full model.

Limits to know

• getVideoTranscript, getVideoChapters, getFrames and getScreenshots do not work with Instant Replay Jams.
• getFrames works only on video Jams hosted on Cloudflare Stream.
• Jam recommends working with one Jam link at a time to avoid filling the context window.
• Jam notes that some tools use Google's Gemini, and says it opts out of training on customer data.

Questions

Does Jam have an official MCP server?

Yes. Jam hosts it at https://mcp.jam.dev/mcp and documents setup for VS Code and other clients.

Can the agent delete my Jams?

The server exposes deleteJam and deleteFolder, and they are permanent. Use SAFE or TRUST permission mode so Andromity asks before running them.

Does the agent see Jams I can't open?

No. Jam says MCP access mirrors your existing Jam permissions.

Sources

This guide is based on Jam’s own documentation. The app controls its server, so tools can change; check the source for the current list.

• Jam MCP documentation

Jam is a trademark of its owner. Andromity is not affiliated with or endorsed by Jam.