Skip to main content

Claude Code

You can connect Claude Code on your computer to your BrowseWiz extension. BrowseWiz then shows up in Claude Code as an MCP server named browsewiz, with BrowseWiz's Sheets, Calendar and browser tools.

The connection runs entirely on your computer: Claude Code starts a small local program, @browsewiz/mcp, and the BrowseWiz extension connects to it at 127.0.0.1. The connection doesn't go through BrowseWiz's servers; only browsewiz_browse tasks do, as the browser agent does in chat.

Set it up​

  1. In BrowseWiz, open Options → Tools and find the Claude Code section.

  2. Turn on Connect Claude Code. BrowseWiz creates a connection token and shows a setup command:

    claude mcp add browsewiz -e BROWSEWIZ_TOKEN=<your token> -- npx -y @browsewiz/mcp

  3. Click Copy, paste the command in a terminal and run it. You need Node.js 20 or later installed for npx.

  4. Restart Claude Code.

While Claude Code is running, the section's status shows Connected. Otherwise it shows Waiting for Claude Code. After Claude Code starts, BrowseWiz connects within about 30 seconds.

Claude Code's calls work with the side panel closed, but the browser must be running with BrowseWiz in it.

The pairing belongs to this browser, not to your BrowseWiz account: signing out or switching accounts leaves it connected. Deleting your account removes it.

Sheets and Calendar tools​

Claude Code can use BrowseWiz's own Google Sheets and Calendar tools, with the same names and the same rules as in BrowseWiz chat:

  • Spreadsheet tools: listSpreadsheets, createNewSpreadsheet, readHeader, readSpreadsheet, findRows, upsertRows, setColumnTypes, formatCells, formatWorksheet, appendRows, insertRows, deleteRows, updateRow, addWorksheet, deleteWorksheet, renameWorksheet and deleteSpreadsheet.
  • Calendar tools: createGoogleCalendarEvent, searchGoogleCalendarEvents, updateGoogleCalendarEvent and deleteGoogleCalendarEvent. They use the calendar you set up in Options → Tools, and Claude Code also receives that calendar's name and description.

Claude Code gets a toolset only while its switch is on in BrowseWiz (the side panel's Tools menu or Options → Tools). Turn a switch on or off and Claude Code's tool list follows within a few seconds. If Claude Code calls a tool whose switch is off, the call returns a message saying which switch to turn on, and where.

A call fails if its result is larger than 1 MiB, for example a very large spreadsheet read. A call that takes longer than 120 seconds times out.

Sign in to Google first. Claude Code can't open the Google sign-in window, and Google sign-in is separate for each toolset:

  • Sheets: in Options → Tools, click "Sign in to Google" next to Spreadsheet tools. The button shows only while you aren't signed in.
  • Calendar: in Options → Tools, click "Configure" next to Calendar tools, then "Create Calendar" or "Update Calendar".

Until then, Claude Code's calls to that toolset fail with a message telling you which button to click, with a link to Options → Tools.

Permission prompts. BrowseWiz shows no approval card for these calls: Claude Code asks you before each tool call instead. The read-only tools (listSpreadsheets, readHeader, readSpreadsheet, findRows, searchGoogleCalendarEvents) are marked as read-only, and the tools that delete or rename (deleteRows, deleteWorksheet, renameWorksheet, deleteSpreadsheet, deleteGoogleCalendarEvent) are marked as destructive. If you allow all mcp__browsewiz__* tools in Claude Code, it can delete rows, worksheets, spreadsheets and events without asking. Claude Code can reach only spreadsheets BrowseWiz created, and only BrowseWiz's own calendar.

The data these tools read goes to Claude Code, and from there to Anthropic or whichever AI provider Claude Code uses. See the privacy policy, section 6.

Browser tools​

While the browser agent is switched on in BrowseWiz, Claude Code also gets four browser tools:

  • browsewiz_open_tab opens a web page (an http:// or https:// address) in a new background tab in the BrowseWiz Tabs group and returns its tab ID.
  • browsewiz_navigate loads another http(s) address in one of those tabs.
  • browsewiz_list_tabs lists the ID, address and title of every tab in the BrowseWiz Tabs groups.
  • browsewiz_browse hands a task to the BrowseWiz browser agent, which carries it out in one of those tabs (reading the page, clicking, typing, pressing Enter) and reports back with STATUS: success, partial or blocked.

BrowseWiz tabs only. These tools only work in the BrowseWiz Tabs groups: tabs BrowseWiz opened, and tabs you gave BrowseWiz access to in a chat earlier, which browsewiz_list_tabs shows too. Claude Code can't take over any other tab, and can't ask for access to one.

Grant tab access first. The browser tools need Chrome's permission to manage tabs. If Options → Tools → Claude Code shows a Grant tab access button, click it and accept Chrome's prompt. Until then, the browser tools return "Grant tab access in BrowseWiz".

Safety check. browsewiz_browse runs unattended, like a scheduled task: there are no approval cards. Instead, every click, typing and Enter goes through BrowseWiz's safety check, measured against the task text Claude Code sent. An action the check flags, or can't check, is refused and the task ends as blocked. The task text is all the check knows about what you want, so Claude Code's permission prompt for browsewiz_browse is where you decide whether a task should run. Claude Code's own browsewiz_open_tab and browsewiz_navigate calls aren't safety-checked.

Credits. browsewiz_browse uses the browser agent's model and your BrowseWiz credits, as in chat, so you need to be signed in to BrowseWiz in the side panel. The other three browser tools use no model and no credits.

One task at a time. Only one browsewiz_browse task runs at a time; another call while one runs is refused at once. A task stops after 10 minutes, and stops as soon as you cancel it in Claude Code. The tab tools keep working while a task runs.

Page content the browser agent reads, its reports, and the addresses and titles of your BrowseWiz tabs go to Claude Code, and from there to its AI provider.

The status tool​

Ask Claude Code "is BrowseWiz connected?" to use browsewiz_status. It returns:

  • whether the extension is connected;
  • the extension's version;
  • whether you are signed in to BrowseWiz;
  • whether the browser agent, spreadsheet and calendar tools are switched on.

It doesn't send your email, sign-in tokens or anything about your tabs. If the extension isn't connected, it lists the steps above.

Only one Claude Code session can be connected at a time. If another session (or another program) already uses the connection's port, 47391, the status tool says so: close the other session and try again.

Keep your token safe​

Claude Code keeps the token in its MCP settings file (~/.claude.json) in plain text. Anyone with the token and access to your computer could connect to your extension in Claude Code's place. Don't share the setup command.

Click Reset token to make a new token. The old one stops working at once, and Claude Code disconnects until you run the new command (remove the old server first with claude mcp remove browsewiz) and restart Claude Code.

Disconnect​

  • Turn off Connect Claude Code in Options → Tools. BrowseWiz deletes the token and closes the connection.
  • To remove BrowseWiz from Claude Code too, run claude mcp remove browsewiz.
Last updated on