Enquire docs
    Enquire docs
    Getting startedUser guide
    ArchitectureBrowser toolsProcedures
    Claude Code integrationExtension guide
    DeploymentRoadmapBenchmarks
    Get Started

    Getting started

    5-minute setup — extension, sign-in, MCP client, first call.

    5-minute setup. From zero to "Claude Code drives my browser" in three steps.

    What you'll have when you're done

    • The Enquire extension installed in your Chrome
    • An account at app.enqr.dev with a bearer token
    • Your MCP client (Claude Code / Cursor / Claude Desktop) calling enquire__navigate, enquire__click, enquire__extract, etc. against your real browser

    Prereqs

    • Chrome 116+ (the extension uses MV3 + offscreen documents)
    • An MCP-aware client: Claude Code, Claude Desktop, Cursor, Cline, or any other client that speaks MCP

    You do not need an LLM API key to install. You'll need one (or a running local model) if you want the extension's built-in chat/agent panel to work — Enquire supports Anthropic, OpenAI, Google AI, Bedrock, Azure, plus local Ollama, in-browser WebLLM, and transformers.js. If you're only using Enquire as an MCP backend (typical), the LLM lives in your MCP client.

    Edit on GitHub

    User guide

    Day-to-day use of the Enquire Chrome extension's side panel.

    On this page

    PrereqsStep 1 — Install the extensionOption A: Signed beta buildOption B: Load unpacked for local developmentStep 2 — Sign inStep 3 — Add Enquire to your MCP clientClaude Code (recommended: CLI)Other clients (manual config)Step 4 — First callTools availableTry it on a logged-in siteTroubleshooting"Browser extension not connected" (-39001)"Invalid or expired token" (401)Tools don't appear in MCP clientSign-in page is blank in the extension popupAgent drove the wrong tabWhere to nextPrivacyHelp

    Step 1 — Install the extension

    Option A: Signed beta build

    A signed Chrome extension .crx is available on request — email support@enqr.dev and we'll send a download link plus install instructions.

    Option B: Load unpacked for local development

    From the enquire repo, build the extension:

    npm install
npm run build:store

    Then in Chrome:

    1. Open chrome://extensions
    2. Toggle Developer mode on (top right)
    3. Click Load unpacked
    4. Select dist/chrome-mv3-store/ from the cloned enquire repo

    Enquire's icon should appear in your toolbar.

    Step 2 — Sign in

    1. Open https://app.enqr.dev/sign-in
    2. Click Create account, enter email + password (8+ chars)
    3. You land at https://app.enqr.dev/app — your dashboard.

    Now connect the extension:

    1. Click the Enquire icon in Chrome's toolbar → Settings
    2. Mode → click Cloud
    3. Sign in with the same email + password (or pick a dev userid if running locally)
    4. Click the Bridge tab — you should see "Bridge Running · tunnels: 1"

    If it doesn't connect, the Bridge page's debug panel will tell you why (usually: bad URL or expired token; clicking Reset bridge + auth + signing in again fixes it).

    Step 3 — Add Enquire to your MCP client

    Open https://app.enqr.dev/app/setup — your token is pre-filled, with Copy CLI command, Copy config, and Copy token buttons.

    Claude Code (recommended: CLI)

    claude mcp add --transport http enquire 'https://bridge.enqr.dev/mcp' \
  --header 'Authorization: Bearer <YOUR_TOKEN>' --scope user

    This writes to ~/.claude.json (Claude Code's actual config — not ~/.claude/mcp.json, which Claude Code does not read). Restart Claude Code (Cmd-Q, reopen), then /mcp should show enquire ✓ Connected.

    Other clients (manual config)

    Same JSON shape works in any MCP-aware client:

    {
  "mcpServers": {
    "enquire": {
      "type": "url",
      "url": "https://bridge.enqr.dev/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}
    ClientPath
    Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.json (macOS) / %APPDATA%/Claude/claude_desktop_config.json (Windows)
    CursorSettings → Features → MCP → Edit mcp.json
    ClineSettings → MCP Servers → Edit configuration
    OtherLook for "MCP servers" or "context servers" — same JSON shape

    Restart the client. The server "enquire" should appear in your tool list.

    Step 4 — First call

    In Claude Code, type:

    use enquire to open https://example.com and tell me the page title

    What happens:

    1. Claude Code calls enquire__navigate({url: "https://example.com"})
    2. Bridge routes to your tunneled extension
    3. Your Chrome opens example.com in a new tab
    4. Claude Code calls enquire__read_page({})
    5. Extension extracts the text, sends it back
    6. Claude Code reports "Example Domain"

    You should see the tab open in your Chrome (the agent literally drove your browser).

    Tools available

    ToolWhat it does
    enquire__navigateOpen a URL in the active tab
    enquire__clickClick a DOM element by CSS selector
    enquire__extractPull text or attribute values from selectors
    enquire__fill_formFill input fields by selector
    enquire__scrollScroll page or container
    enquire__waitWait for a selector or duration
    enquire__read_pageGet the page's readable text + metadata

    Try it on a logged-in site

    This is the killer demo:

    use enquire to open https://github.com/notifications and summarise my unread mentions

    If you're logged into GitHub in your Chrome (which you are), Enquire walks in with your existing session, reads the notifications page, and reports back. No re-auth, no CAPTCHA, no browser fingerprint hacks — just your real session.

    Same trick works on Gmail, Notion, Linear, Slack, Calendar, Sheets, etc.

    Troubleshooting

    "Browser extension not connected" (-39001)

    The bridge can't reach your Chrome.

    • Bridge page in extension → check the debug panel:
      • cloudMode should be true
      • authToken should be (set)
      • relayUrl should be wss://bridge.enqr.dev/ws
      • tunnels (under "Recent WebSocket upgrade attempts") should show accepted for your userId
    • If cloudMode: false → click Cloud → Sign in in Settings
    • If relayUrl looks wrong → click Reset bridge + auth on the Bridge page, then sign in again

    "Invalid or expired token" (401)

    Your token rotated (you signed out somewhere, or it's been 30 days).

    • Re-copy from https://app.enqr.dev/app/setup and update your MCP client config. Restart the client.

    Tools don't appear in MCP client

    • Restart the client after editing mcp.json
    • In Claude Code: /mcp → check the server list. If enquire is missing, check the JSON syntax in mcp.json (commas, brackets)
    • Check the bridge is reachable: curl https://bridge.enqr.dev/healthz should return {"status":"ok",...}

    Sign-in page is blank in the extension popup

    The Cloud mode prompt was replaced with an inline form in v0.1.0. If you see a blank popup, your extension is older than that — re-build with npm run build:store and re-load in chrome://extensions.

    Agent drove the wrong tab

    The agent operates on the active tab. Click into the tab you want the agent to use, then try again. (We're shipping a tabId parameter in a future version to make this explicit.)

    Where to next

    If you want toRead
    Pick an LLM provider for the extension's own chatExtension guide
    Understand the architectureArchitecture
    Compare against agent-browser, chrome-devtools-mcpBenchmarks
    Self-host the bridge + APIDeployment
    See what's plannedRoadmap

    Privacy

    Enquire stays out of your way:

    • The pages you visit, what you click, what's on screen stay in your Chrome unless you explicitly ask the agent to do something that requires sending content (e.g. summarise this page → page text goes to whichever LLM you configured).
    • Your accounts and passwords — never read, never transmitted.
    • What's on our servers: email, signed procedures you save, token- count usage logs, and conversations you opt into syncing. Full details at https://app.enqr.dev/privacy.

    Help

    • Bug or weird behaviour: email support@enqr.dev
    • Privacy / data deletion: privacy@enqr.dev
    • Anything else: start at Getting started or email support.