Hosted MCP server/Development Official

Official Jam MCP server

Hosted at mcp.jam.dev·Streamable HTTP

Jam captures screen recordings and automatic context when people report issues. Its MCP connector hands an assistant bug-report context, reproduction details, and recorded evidence for debugging and product-feedback workflows. Access uses OAuth at https://mcp.jam.dev/mcp; run opencode mcp auth jam (or the equivalent sign-in step) after adding the server.

mcp.jam.dev Streamable HTTP OAuth Source checked Oct 31, 2026 Server not checked yet Reviewed 2026-11-16
About

Where it fits

Engineers and support teams who need bug report context and reproduction steps while debugging.

  • Turn a recorded bug report into a ticket
  • Extract reproduction steps from the report context
  • Review the captured evidence before debugging

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds Jam as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http jam https://mcp.jam.dev/mcp --scope project
  2. 02

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://mcp.jam.dev/mcp
Host
mcp.jam.dev · /mcp
Transport
Streamable HTTP
Authentication
OAuth
Server name
jam
Listing type
Official provider listing

The installer uses the server name jam. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that jam appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Turn a recorded bug report into a ticket. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. The provider page was available when we checked.

Provider page available on Oct 31, 2026. A response does not guarantee the server is safe or that sign-in and tools will work.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
  • The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Jam documentationhttps://jam.dev/docs/jam-mcp.md