jailbreak

Jailbreak-MCP is a middleware MCP server that exposes configured resources and prompts as tools, enabling even clients with restrictive MCP implementations to access a broader set of capabilities. It wraps the underlying jailbreak-mcp package so you can select specific modes that reveal only the tools, prompts, and resources you need for a given task. This helps manage the MCP tool/tool and context-window usage across multiple servers by switching between modes at runtime. The server is started via npx with a configuration file (mcp.json) that defines the jailbroken tools, prompts, and resources across one or more servers.

Once running, you can configure modes to whitelist exact tools, prompts, and resources for each server. The default example mode exposes a curated set of tools like echo, add, and longRunningOperation, along with prompts like simple_prompt and complex_prompt, and resources such as test://static/resource/1. You can switch between modes on-the-fly to tailor the available capabilities to the current task, helping to avoid overloading your agent’s context window while keeping broader MCP protocol coverage available when needed.

Prerequisites:

• Node.js and npm (or corepack if you prefer).
• Basic familiarity with editing JSON configuration files.

Installation steps:

1. Install Node.js and npm from https://nodejs.org/
2. Ensure you have npx available (comes with npm).
3. Create or locate your mcp.json configuration file (example provided in the README).
4. Place the mcp.json configuration wherever you want the server to read it (the example uses ~/.cursor/jailbreak.mcp.json).

Example workflow to start using the Jailbreak MCP server:

• Save the example configuration to ~/.cursor/jailbreak.mcp.json with the proper tools/prompts/resources you want.
• Start the server via the MCP launcher (as configured with npx):

# When using the provided mcp.json, start the server with whatever runner you normally use for MCP servers.
# For the example in this project, you would rely on your MCP client or launcher to parse mcp.json and invoke the npx jailbreak-mcp@latest command.
# If you want to run directly via npx for testing:
npx jailbreak-mcp@latest /optional/path/to/jailbreak.mcp.json

5. Confirm the server starts and exposes the tools as defined in the active mode. You can then switch between modes to expose different toolsets as needed.

Tips and caveats:

• The jailbreak server relies on a mcp.json configuration that defines mcpServers and modes. The keys under modes determine which tools, prompts, and resources are exposed for a given server when that mode is active.
• The server prioritizes command-line arguments, then environment variables, then a default config file at the path you provide. This means you can override CONFIG_PATH via env or CLI to point to a different config.
• If you enable many tools across multiple servers, monitor your agent’s context window to avoid depleting it too quickly.
• You can set mode configurations to true to expose everything for a given server, or provide precise lists of tools/prompts/resources to tailor behavior to a task.
• The current README notes that the initial focus is on tools, with plans to extend to other protocol features; ensure your client is compatible with the exposed tool list.
• If you encounter issues with tool discovery, verify the mcp.json schema and that the server is reading the correct file path (CONFIG_PATH or the default location).