Orca Main documentation

Orca Main lets an AI agent drive your real Chrome browser through MCP. You install a Chrome extension, connect it to this hub, generate a short auth code, and paste that code into the agent. No API token goes in the MCP URL.

Chrome extension

Download the plugin

Public zip hosted on this hub. Unzip and Load unpacked in Chrome.

Download orca-main-extension.zip

Stable URL: /extension.zip

How it fits together

Agent  --MCP HTTP-->  Orca hub /mcp/  --WebSocket-->  Chrome extension  --CDP/DOM-->  your tabs
  1. Install the Orca Chrome extension and turn Connect on.
  2. Point the extension at this server and paste your dashboard API key.
  3. Click Generate auth code and give the code to your agent.
  4. Configure the agent’s MCP client with the hub URL only (no auth header).
  5. The agent calls orca_connect once, then passes auth_code on every tool.

Install the extension

  1. Download orca-main-extension.zip from the button above.
  2. Unzip it somewhere permanent (Chrome must keep reading that folder).
  3. Open chrome://extensions.
  4. Enable Developer mode (top right).
  5. Click Load unpacked and select the unzipped folder (it should contain manifest.json).
  6. Pin the Orca icon from the puzzle-piece menu so it is easy to open.
Chrome Web Store packaging is not required. “Load unpacked” is the supported install path. Updates: download the new zip, extract over the same folder you already loaded, then click Reload on the existing Orca card in chrome://extensions. Do not Load unpacked again from a new folder — that creates a second extension and drops your saved server URL / auth code. If the hub raises the minimum version, older builds are blocked until you update — the FAB/popup will show Update required with a download link.

Configure the extension

  1. Click the Orca toolbar icon (popup) or the floating Orca icon on any page (FAB).
  2. Set Server URL to: 
    https://orca.ilazzy.com
  3. Sign in to the dashboard, copy Your API key, and paste it into the extension.
  4. Turn Connect on. The popup pill should read Connected after you generate a code.

Leave Connect on while the agent is working. If the extension goes offline, tools return connection_closed until you reconnect with the same code.

Connect and get an auth code

  1. Open the FAB on any page (Auth tab) or the toolbar popup.
  2. Optionally pick token validity (30 minutes, 2 days, or 30 days).
  3. Click Generate auth code. The extension mints a new short code (invalidating any previous one) and opens the WebSocket relay.
  4. Copy the code and paste it into your agent chat: “Orca auth code is ABCD1234.”
  5. Copy the MCP URL into your agent’s MCP settings if you have not already: 
    https://orca.ilazzy.com/mcp/
Reconnects reuse the same stored code. Regenerate only when you want a new pairing. Codes expire after the TTL you chose. Near expiry, the page icon offers Extend — prefer Extend over regenerating mid-task so the agent can keep the same code.

Tell the agent this workflow:

  1. Call orca_connect once with the code.
  2. Pass auth_code on every later Orca tool call.
  3. Do not put the code in the MCP URL or an Authorization header.

Configure MCP in agents

Use Streamable HTTP MCP. Configure URL only — no headers, no ?token=. Identity is the auth_code argument on tools.

Cursor

Settings → MCP → Add new MCP server (HTTP / URL):

{
  "mcpServers": {
    "orca-main": {
      "url": "https://orca.ilazzy.com/mcp/"
    }
  }
}

After saving, reload MCP tools if Cursor cached an old list. Paste the auth code in chat when asked.

VS Code / GitHub Copilot Chat

In MCP settings (or .vscode/mcp.json / user MCP config), add an HTTP server:

{
  "servers": {
    "orca-main": {
      "url": "https://orca.ilazzy.com/mcp/"
    }
  }
}

Exact key names vary by Copilot / MCP UI version — the important part is the URL ending in /mcp/.

Claude Desktop / Claude Code (stdio fallback)

Claude Desktop historically uses stdio MCP. Use the optional mcp_bridge if HTTP MCP is not available: 

{
  "mcpServers": {
    "orca-main": {
      "command": "python3",
      "args": ["-m", "mcp_bridge"],
      "env": {
        "ORCA_SERVER_URL": "https://orca.ilazzy.com",
        "ORCA_AUTH_CODE": "PASTE_CODE_HERE"
      }
    }
  }
}

Prefer HTTP MCP when the client supports it so you do not bake the auth code into config.

Windsurf, Cline, Continue, and other HTTP MCP clients

Add a remote / HTTP MCP server with:

https://orca.ilazzy.com/mcp/

Then paste the extension auth code into the agent conversation.

What the agent should do after connect

  1. orca_connect({ auth_code }) once — read instructions, the action catalog, and knowledge_reminder.
  2. Put click + wait + branch in one orca_browser steps workflow; get_all_tabs before opening new tabs.
  3. Look up site memory with orca_memory op=lookup / list_skills before inventing flows.
  4. Save new learnings with op=save / save_skill.

See knowledge and skills in the plugin

On any page, click the floating Orca icon. The panel has three tabs:

Agents populate these via MCP. You can also edit documentation and knowledge from the dashboard. Refresh the Knowledge tab after an agent saves new entries.

Dashboard

  1. Open /login with the email your tenant admin created.
  2. Copy Your API key into the extension.
  3. Review Connected codes — each minted auth code, whether the extension is online, expiry, and last seen origin.
  4. Manage Actions, site documentation, and knowledge entries for allowed origins.

Troubleshooting