Documentation
Connect Claude Code
Register the connector that ships with Wisp once, and every Claude Code session on this PC can use the browser in the background, signed in to your sites.
Before you start
- Wisp is installed (default folder
%LOCALAPPDATA%\Programs\Wisp). - Node.js 18 or newer is installed (
node --version). - Claude Code is installed and signed in.
Add the MCP server
In Command Prompt:
claude mcp add -s user wisp -- node "%LOCALAPPDATA%\Programs\Wisp\resources\connect\wisp-mcp.js"In PowerShell, use $env:LOCALAPPDATA instead of %LOCALAPPDATA%:
claude mcp add -s user wisp -- node "$env:LOCALAPPDATA\Programs\Wisp\resources\connect\wisp-mcp.js"-s user makes the server available in all your Claude Code sessions, not just the current project. If you installed Wisp somewhere else, point at resources\connect\wisp-mcp.js inside that folder.
Wisp also shows these commands, with the exact path on your PC, in the AI panel under Connect other agents (Claude Code, Codex, Python).
Use it
Start a new Claude Code session and ask for something that needs the browser, for example “open my GitHub notifications in Wisp and summarise them”. If Wisp isn’t running, the connector starts it hidden (tray icon only). Nothing comes to the front and your mouse and keyboard are left alone.
Tabs an agent opens carry an “AI” badge in Wisp. If a site needs a login, sign in yourself inside Wisp; agents don’t type passwords, and saved passwords are not available to them.
Tools
| Tool | What it does |
|---|---|
wisp_tabs | List open tabs (id, url, title). |
wisp_profiles | List profiles (each has its own logins). |
wisp_open | Open a URL in a new background tab and wait for it to load; optional profile. |
wisp_navigate | Send an existing tab to a URL or a search phrase. |
wisp_back | Go back in a tab’s history. |
wisp_read | Visible text of the page, main content first; optional CSS selector. |
wisp_snapshot | Interactive elements with refs like w12 for clicking and typing. |
wisp_click | Click by ref, CSS selector, visible text, or x/y. |
wisp_type | Type into an element; submit presses Enter afterwards. |
wisp_upload | Attach local files (absolute paths) to a page’s file input, like choosing them in Browse. Click the site’s own upload button first if it creates the input on demand. |
wisp_key | Press a key such as Enter, Escape, ArrowDown or ctrl+a. |
wisp_scroll | Scroll by dy pixels (default: most of a screen). |
wisp_wait | Wait for a selector, some text, or a number of milliseconds. |
wisp_eval | Run JavaScript in the page and return the result. |
wisp_screenshot | Screenshot a tab, even in the background; optional full page or file path. |
wisp_close_tab | Close a tab. |
wisp_show_window | Bring the Wisp window to the front, for when you want to see it. |
The connector is a thin bridge to the local API.
Remove it
claude mcp remove -s user wispTroubleshooting
- “node” is not recognized: install Node.js 18+ and open a new terminal.
- Cannot find module …wisp-mcp.js: the path is wrong. Open the AI panel in Wisp and use Open connect folder to see where the connector is.
- “Wisp is not running and Wisp.exe was not found”: the connector looks for Wisp in the default install folder. Start Wisp yourself first, or set the
WISP_EXEenvironment variable to the full path ofWisp.exe. - Token errors: the token is read from
%APPDATA%\Wisp\api.json, which Wisp writes while it runs. Make sure Wisp can start under your Windows user.