# Jam MCP connector The Jam connector brings your bug recordings, console logs, network requests, comments and folders into Claude, ChatGPT and Cursor, so anyone can ask about a jam and get an answer from the actual recording. Source: https://elaichi.ai/connectors/jam/ ## Facts | | | | --- | --- | | Application | Jam | | Category | Application Development | | AI tools | 31 | | Authentication | Connects over OAuth | | Bring your own OAuth app | No | | Native MCP | Yes. Jam builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top | | Support for its tools | jam.dev/contact | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead | ## What you can ask once Jam is connected - Summarize the console errors in the checkout crash jam from yesterday. - Which jams in the Mobile folder mention a failed network request? - Draft a comment on the login bug jam with the repro steps. ## Connect Jam in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Jam. 2. Optionally set Share with, then press Connect. 3. Approve it in Jam. Jam's own window opens. Whoever approves it decides what this connection can reach. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Jam tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Jam MCP connector for Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## Jam MCP connector for ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 3. Leave Authentication on OAuth, then tick the risk acknowledgement. 4. Press Create, then sign in and approve. Works on the web today. The plugin directory lives at chatgpt.com/plugins. ## Jam MCP connector for Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Jam to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Jam tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Jam through Elaichi ### Read the console logs before opening the video Engineering. Ask what errors fired during a jam and which network requests failed, then get the stack of events in order without scrubbing through the recording. ### Turn a customer's jam into a clear ticket Support. Pull the transcript, the steps the user took and the browser details from a jam, and draft the ticket in the words an engineer needs. ### Find every jam that shows the same bug QA. Search jams across folders for a failing request or an error message and see whether the regression is new or has been reported before. ### Summarize what the week's jams are about Product. Ask for the themes across the jams in a folder, with chapters and transcripts summarized, so the Friday review starts with the real picture. ### Pull the frames that show the broken screen Design. Get the screenshots and frames from a jam where the layout breaks, and leave a comment pointing at the exact moment. ### Keep the jam updated after the call Customer Success. After talking to a customer, add a comment with what they said, react to the fix when it lands, and move the jam into the right folder. ## Elaichi vs Zapier MCP vs Composio for Jam All three can connect Jam to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay. | What to check | Elaichi | Zapier MCP | Composio | | --- | --- | --- | --- | | Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. | | Control over Jam tools | Allow or restrict single Jam tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. | | Record of calls | One audit entry per Jam call. | A History tab of tool calls. | A log of every tool call. | | Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. | | Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. | Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026. Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/). ## Frequently asked questions ### How do I connect Jam to Claude? In Elaichi, choose Jam and connect it. Jam's own sign-in opens in your browser, you approve access, and you are done, with no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude can now work with your jams, console logs and comments as you. ### Does Jam work with ChatGPT and Cursor as well as Claude? Yes. Once Jam is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Jam once and every client you use picks it up. ### What can an AI agent actually do with my Jam data? It can read a jam's details, console logs, network requests, user events, screenshots, frames, transcript and chapters, and analyze the video to explain what went wrong. It can search jams, list folders and members, add or edit comments, add reactions, update or move jams, and create or tidy folders. Short, specific asks like "what errors fired in this jam" work better than long sentences. ### Does connecting Jam give the AI access to every jam in my workspace? No. The AI acts as the person who signed in to Jam, so it only sees the jams, folders and comments that person can already open. Elaichi can narrow that further with roles and restrictions, but it can never widen access beyond what Jam already allows that person. ### Can my team share one Jam connection? Yes. One person connects Jam in Elaichi and shares the connection with a team, and nobody else ever handles a credential. Each teammate still signs in to Elaichi as themselves, so every comment, reaction or folder change in Jam is logged under their own name. ### Can I stop an agent from deleting or changing things in Jam? Yes. Restrictions in Elaichi work per action, so you can allow reading jams and console logs while blocking deleting a jam, removing a comment or deleting a folder. A restricted action is never shown to the AI client at all, so no prompt can reach it. ### What happens to a Jam connection when someone leaves? When you offboard a person in Elaichi, their access to Jam through every client ends at once. If Jam was connected through a shared connection, it keeps working for everyone else on the team. If you disconnect Jam once in Elaichi, it disappears from Claude, ChatGPT, Cursor and every other client together. ### Does the Jam MCP connector work with Gemini, Codex, Claude Code or other MCP clients? Yes. Jam is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs. ### Is Elaichi an alternative to Zapier MCP for Jam? Yes. Both let Claude, ChatGPT or Cursor use Jam. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Jam call. ### How is Elaichi different from Composio for Jam? Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Jam: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call. ## All 31 Jam tools Every tool below is callable through https://api.elaichi.ai/mcp once Jam is connected, subject to the toolbox it is in and the restrictions on the caller. - **Get details** (Get). Get a quick snapshot of the Jam: who made it, what happened, and which other tools to try next. - **Get console logs** (Get). Grab the console logs from the Jam. Supports logLevel, limit, and after (page cursor) filters to reduce noise. - **Get network requests** (Get). List every web request from the Jam as JSON. Supports statusCode, contentType, host, method, limit, and after filters, plus bodies (errors by default, or all). - **Get user events** (Get). Read each click, input, and page navigation change in plain language. - **Get metadata** (Get). Read custom key-value metadata set via the jam.metadata() SDK: user IDs, app versions, feature flags, and more. - **Get screenshots** (Get). Get every screenshot from a screenshot Jam for visual inspection. - **Get video transcript** (Get). Get the spoken transcript from a video Jam where the microphone was enabled, in WebVTT format with timestamps. - **Get video chapters** (Get). Get AI-generated chapter markers for a video Jam: titled segments with start and end timestamps. Text only. - **Analyze video** (Action). Analyze a Jam video recording to extract insights, detect issues, and provide structured feedback. - **Get frames** (Get). See what was on screen in a video Jam. Return frames at specific timestamps, evenly across a window, or one labeled overview grid spanning the whole recording. - **Search jams** (Search). Search Jams by text across titles, descriptions, comments, linked issues, and transcripts. Filter by author, folder, type, date, and more. - **List members** (List). Browse your team members. - **List folders** (List). Browse available folders. - **Create comment** (Create). Add Markdown comments to a Jam, optionally mentioning a teammate to notify them. - **Edit comment** (Action). Rewrite a comment you left earlier, so an agent can correct its own note instead of stacking a follow-up. - **Delete comment** (Delete). Delete a comment you wrote, along with its attachments. - **Add reaction** (Add). React to a comment. Handy for acknowledging one you’ve already acted on. - **Remove reaction** (Delete). Take back a reaction you left on a comment. - **Update Jam** (Update). Rename a Jam, rewrite its description, or move it between folders using a folder ID or folder name. - **Delete Jam** (Delete). Delete a Jam. It leaves your lists and search, and there is no way to restore it. - **Create folder** (Create). Create a folder to organize Jams into. Returns the folder’s ID and short ID so a follow-up updateJam can file a Jam into it. - **Update folder** (Update). Rename a folder, addressed by its name, ID, or short ID. - **Delete folder** (Delete). Delete a folder and every Jam inside it, none of them restorable. Returns how many Jams went with it. - **List recording links** (List). List the team’s recording links, newest first, with cursor pagination and an includeRevoked option. - **Get recording link** (Get). Get one recording link by its public ID. - **List recording link jams** (List). List the Jams recorded through a link, by public ID, with cursor pagination. - **Create recording link** (Create). Create a reusable recording link, optionally targeting a folder, connected domain, or expiration. - **Update recording link** (Update). Edit a link’s name, folder, reference, Jam title, expiration, or metadata by public ID (revoked links can’t be edited). - **Delete recording link** (Delete). Revoke a link by its public ID (soft-delete, so collected Jams stay). - **List recording URLS** (List). List the team’s connected recording domains. - **Get recording URL verify link** (Get). Start verifying a connected domain and return a link a human opens to confirm it.