Getting started

Set up Secure Browser MCP

Install the server, connect it to an MCP client, and try the local storefront. This follows the same short, runnable path as the project's code-storage-style guides: prerequisites, one command at a time, then a verification step.

Prerequisites

Bun installed.
A Chromium-based browser. The server checks SBM_CHROME_PATH first, then common Chrome, Chromium, Brave, and Edge locations.
For production secrets: Turnkey Secrets access and API credentials. The mock backend works without them.

1. Install and verify

git clone https://github.com/tkhq/secure-browser-mcp.git
cd secure-browser-mcp
bun install
bun test

The test suite drives a local storefront and asserts that plaintext does not reach server output.

2. Add the MCP server

Claude Code can launch the server directly over stdio:

claude mcp add secure-browser -- bun run /path/to/secure-browser-mcp/src/index.ts
bun run skill:install -- --claude

Use --codex instead to install the bundled skill for Codex. The server itself works with any MCP client that supports stdio.

3. Try the fixture

bun run demo:fixture
# In a second terminal:
bun run dev

Open the fixture at http://localhost:4173. It includes a login route and a checkout route with seeded mock secrets.

4. Use Turnkey Secrets

Set the following environment variables before starting the server:

export TURNKEY_API_PUBLIC_KEY=...
export TURNKEY_API_PRIVATE_KEY=...
export TURNKEY_ORGANIZATION_ID=...

Keep API credentials outside your MCP configuration and transcripts. A secret becomes fillable only after it has an immutable destination binding.