Coming next

JamJet Gateway

An open-source MCP proxy that applies JamJet policy to MCP traffic from Claude Desktop, Cursor, and any MCP-aware agent.

Today, JamJet's safety layer runs as an SDK inside your agent's process (see the 60-second demo). Gateway will run as a standalone process and apply the same policy across networked MCP traffic — without changing your agent code.

What you'll be able to do

npx jamjet-gateway init
jamjet-gateway add github
jamjet-gateway add filesystem
jamjet-gateway run

The same policy model, applied at the network

tools:
  github.search:              { allow: true }
  github.create_pull_request: { approval: required }
  filesystem.read:            { allow: true }
  filesystem.write:           { approval: required }
  filesystem.delete:          { block: true }
  shell.exec:                 { block: true }

Every Gateway decision lands in the same audit stream as in-process JamJet decisions: the trace ID, the policy that matched, the decision, and a replayable record of the tool call. One policy model, two enforcement points.

Why a gateway, in addition to the SDK

• Desktop agents. Claude Desktop and Cursor talk to MCP servers directly. There is no SDK seam to insert policy into. A gateway lives on the wire between them.
• Heterogeneous fleets. Python, Java, and TypeScript agents can all share a single policy file by routing MCP traffic through one Gateway.
• Untrusted third-party MCP servers. The proxy can sanitize, rate-limit, and audit calls before they leave your machine or network.

Stay in the loop

• Star jamjet-labs/jamjet to follow.
• Try jamjet demo mcp-tool-policy today — same policy model, MCP-shaped envelope.
• Join Discord for early access.