iframer-toolkit

Browser access for AI agents when normal fetching fails. Give Claude, Codex, or any MCP-compatible agent a real browser — with session persistence, stealth fingerprinting, encrypted credential storage, and automatic captcha solving, and most af all, API Reverse Engineering.

Example:

Ships as:

• CLI (iframer-toolkit / iframer) — browse, screenshot, credentials, sessions, reverse-engineer APIs
• MCP server — plugs directly into Claude Code or Codex so agents can drive the browser themselves
• Self-hosted Docker server (optional) — adds live headful browsing over noVNC for remote/multi-user setups

Install

npm install -g iframer-toolkit

Then pull in the runtime dependencies (Chrome for Testing + MCP registration):

iframer-toolkit install deps

This is shorthand for:

iframer-toolkit install chromium   # downloads Chrome for Testing to ~/.iframer
iframer-toolkit install-mcp        # registers the MCP server in ~/.claude.json and ~/.codex/config.toml

Restart Claude Code or Codex and the iframer tools will be available.

Note: If you prefer, your agent can run iframer-toolkit install deps for you — it'll figure the rest out.

Quick start

Once installed, you can either drive the browser via the CLI directly, or ask your agent (Claude Code / Codex) to do it for you via the MCP.

CLI:

iframer-toolkit status                                      # system + browser modes
iframer-toolkit browse https://example.com --extract 'document.title'
iframer-toolkit screenshot https://news.ycombinator.com -o /tmp/hn.png
iframer-toolkit credentials add github.com                  # interactive masked prompt
iframer-toolkit reverse-engineer https://some-spa.com       # capture the APIs it calls
iframer-toolkit --cache                                     # list cached domains

From Claude Code or Codex (after install-mcp):

"Log into my account on example.com and extract the latest invoice."

The agent will call knowledge first (to see if a direct-API path is cached), fall back to credentials + execute if not, auto-escalate browser modes if a site blocks headless, and return the result. No copying cookies, no proxies, no manual login.

How it works

Claude / Codex (MCP) ──→ iframer MCP server ──→ Iframer (local)
                                                    ├─ patchright (stealth Chromium)
                                                    ├─ Chrome for Testing
                                                    └─ SQLite at ~/.iframer — one file for
                                                       encrypted credentials, session state,
                                                       and per-domain knowledge cache

By default, install-mcp runs in local mode: no Docker needed. The MCP spawns a stealth-patched Chromium (via patchright) on your machine. install-mcp registers the server in both Claude Code (~/.claude.json) and Codex (~/.codex/config.toml).

One credential store for every browser mode. Stored credentials, session cookies/localStorage, and the knowledge cache all live in a single SQLite file at ~/.iframer/iframer.db. Store a password once (via CLI or MCP) and every mode — headless, binary-headful, docker-headful — uses the same row. No split-brain between modes.

Auto-escalation. When a pipeline is blocked in headless (bot detection, captcha), iframer transparently retries in binary-headful and then docker-headful without a round-trip to the agent. The mode that worked is recorded in ~/.iframer/domain-modes.json so the next run on that domain starts at the right mode.

Knowledge cache. After every successful run, iframer writes a per-domain markdown file at ~/.iframer/knowledge/<domain>.md recording which cookies / localStorage keys / headers the site uses for auth, plus any API endpoints observed along the way. Next time the agent needs data from that domain, it reads the cache first — if there's a direct-API path, it skips the browser entirely. See Knowledge cache below.

For live remote viewing, multi-user, or Linux server deployments, see Self-hosting with Docker below.

CLI reference

iframer-toolkit <command> [args]

Pipeline:
  execute <pipeline.json|json>     Run a pipeline of browser steps
    --mode <mode>                  Force browser mode (headless|binary-headful|docker-headful)
    --capture-api                  Record XHR/fetch requests during execution
    --continue-on-error            Don't stop on step failure
    --timeout <ms>                 Stale-state timeout (default: 20000)

Quick actions:
  browse <url>                     Headless fetch with JS rendering
    --extract <js>                 Evaluate JS and return result
    --html                         Return full page HTML
    --wait-for <selector>          Wait for element before extracting
    --sessionless                  Skip session persistence
  screenshot <url>                 Take a screenshot of a URL
    --annotate                     Overlay element badges with refs
    -o, --output <path>            Output file path
  reverse-engineer <url|file>      Capture API calls a site makes
    --output <dir>                 Save directory
    --typed                        Generate TypeScript

Session:
  session stop                     Stop and save cookies/localStorage
  session clear                    Wipe stored session data
  session status                   Check session state

Credentials:
  credentials add <domain>         Store login credentials (encrypted)
    --username <user>              Username or email
    --password <pass>              Password (interactive masked prompt if omitted)
    --totp-secret <secret>         TOTP secret for 2FA
  credentials list                 List domains with stored credentials
  credentials remove <domain>      Delete credentials for a domain

Knowledge cache:
  --cache                          List all cached domains
  --cache <domain>                 Print the cached knowledge for one domain
  --clear-cache                    Wipe all cached knowledge
  --clear-cache <domain>           Wipe one domain's cache
  knowledge list                   Same as --cache
  knowledge get <domain>           Same as --cache <domain>
  knowledge clear [domain]         Same as --clear-cache [domain]

Setup:
  install chromium                 Download Chrome for Testing
  install mcp                      Register MCP server in Claude Code and Codex
  install deps                     Run both of the above
  install-mcp [--dev]              Same as `install mcp`
  remove-mcp [--dev]               Remove iframer MCP from Claude Code and Codex

Browser:
  modes                            Show available browser modes
  status                           Show system status

The binary is available as either iframer-toolkit (full name) or iframer (short alias). npx iframer-toolkit ... also works without a global install.

MCP tools

Once the MCP is registered, the agent has access to:

• status — system health, session state, stored credentials, available browser modes
• knowledge — read / list / clear the per-domain knowledge cache. Agents are told to check this before every execute or browse — if the cache has a direct-API path for the data, the browser doesn't launch at all.
• execute — run a pipeline of browser steps (navigate, click, fill, human-click, human-type, scroll, wait, evaluate, extract, keyboard, login, solve-captcha, screenshot, snapshot, find). Each step has a 20s stale-state timeout. On failure, returns the exact step, error type, and a screenshot of the page at the point of failure. Auto-escalates browser modes transparently on bot-block.
• browse — fast headless fetch with session persistence for pages that don't need a full pipeline
• reverse-engineer — capture the APIs a site calls (feeds into the knowledge cache so future runs can skip the browser)
• session — stop (save state) or clear (wipe)
• credentials — store (secure form via MCP elicitation), list. The store action will refuse to overwrite existing credentials unless explicitly told to (force: true) — this blocks the common "login failed, re-ask for password" anti-pattern when the real problem is browser mode / bot detection.

Session persistence

Session data (cookies + localStorage) and credentials are stored in SQLite at ~/.iframer/iframer.db and encrypted with AES-256-GCM. Data is automatically re-injected on the next execute or browse so agents stay logged in across restarts — and across browser modes: a session captured in binary-headful will transparently load into headless on the next run.

The encryption key lives at ~/.iframer/secret (0600 permissions), generated on first install-mcp. Set IFRAMER_SECRET in your environment to override it — useful if you want to synchronize the key across multiple machines.

Knowledge cache

Every successful execute run updates a plain markdown file at ~/.iframer/knowledge/<domain>.md — human-readable, grep-able, and editable. Each file captures:

• Which cookies, localStorage keys, and headers are load-bearing for authentication (names only — values stay encrypted in the session store)
• Which API endpoints the site called during the run (with method, path, example curl, and status code)
• Which browser mode last worked for the domain
• Notes about captcha/bot-detection behavior

The MCP knowledge tool exposes this to the agent with get, list, and clear actions. Agents are instructed to call it before every browser-touching tool — if the cache already knows a direct-API path for the data the user is asking about, the agent hits the API directly and never launches a browser. First request takes seconds; repeat requests on the same domain take milliseconds.

Inspect the cache yourself:

iframer-toolkit --cache                     # list all cached domains
iframer-toolkit --cache figma.com           # print the markdown for one domain
iframer-toolkit --clear-cache               # wipe all cached knowledge
iframer-toolkit --clear-cache figma.com     # wipe one domain

Captcha solving

iframer auto-detects and solves reCAPTCHA and hCaptcha using Claude's vision API. Use the solve-captcha step in a pipeline:

{ "type": "solve-captcha" }

Requires ANTHROPIC_API_KEY in your environment.

Environment variables

Self-hosting with Docker

The Docker server adds a live headful browsing mode over noVNC (watch the agent drive the browser in real time) and lets multiple clients share one browser pool. The Docker path is only used when the pipeline explicitly requests mode: "docker-headful" — headless and binary-headful always run directly on the host even when Docker is up, so host-stored credentials are always visible.

The docker-compose.yml bind-mounts ~/.iframer from the host into the container as /iframer-data and sets IFRAMER_DATA_DIR=/iframer-data, so container and host share the same SQLite file. Credentials stored via the CLI or MCP on the host are immediately visible to docker-headful without any copy step.

1. Clone and configure

git clone https://github.com/EduardoFazolo/iframer-toolkit.git
cd iframer-toolkit
cp .env.example .env
# Edit .env — set ANTHROPIC_API_KEY (for captcha) and IFRAMER_SECRET (for auth)

2. Start

bun run start:docker   # docker compose up --build -d
bun run logs:docker    # tail container logs
bun run stop:docker    # stop containers

3. Point the MCP at it (remote host only)

If you're running Docker on a remote machine and the MCP on a different machine, install the MCP with the remote URL:

IFRAMER_URL=https://your-host:3021 iframer-toolkit install-mcp --dev

When Docker is on the same host as the MCP, no extra setup is needed — the local MCP server will auto-detect the Docker API on localhost:3021 and route only docker-headful requests through it.

4. Watch the browser live

When a docker-headful session is active, open noVNC:

http://your-host:6080

Or run iframer-toolkit watch to auto-open it.

Architecture

Development

git clone https://github.com/EduardoFazolo/iframer-toolkit.git
cd iframer-toolkit
bun install

# Run the CLI from source (no build needed — bun runs .ts directly)
bun run bin/cli.js status

# Run the MCP server from source
bun run src/mcp/server.ts

# Run the Docker API server from source (no Docker)
bun run start   # bun run index.ts

# Rebuild the distributable bundles (dist/cli.cjs + dist/mcp-server.cjs)
bun run build

# Install the locally-built package globally for testing
npm pack
npm install -g ./iframer-toolkit-*.tgz

prepublishOnly runs bun run build automatically, so npm publish always ships a fresh bundle.

License

MIT