Jam
Record screen and collect automatic context for issues
About Jam
Jam captures screen recordings and automatic context for issue reports. Its connector gives assistants bug-report context, reproduction details, and recorded evidence for debugging and product-feedback workflows.
Connection details
https://mcp.jam.dev/mcp- Transport
- Streamable HTTP
- Authentication
- OAuth
Setup
claude mcp add jam --transport http https://mcp.jam.dev/mcpFrequently asked questions
What is the Jam remote MCP server?
The Jam remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.jam.dev/mcp, so AI assistants can connect to it without installing or running anything locally. Jam captures screen recordings and automatic context for issue reports. Its connector gives assistants bug-report context, reproduction details, and recorded evidence for debugging and product-feedback workflows.
How do I connect to the Jam MCP server?
Add the endpoint https://mcp.jam.dev/mcp to any MCP-compatible client such as Claude Code, Codex, Cursor, or VS Code. The setup snippets on this page configure each client in one step.
Does the Jam MCP server require authentication?
Yes. Jam uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.
Which transport does the Jam MCP server use?
Jam exposes a Streamable HTTP endpoint, the current standard transport for the Model Context Protocol, supported by all major MCP clients.
