Install Deputy
Add the extension from the Chrome Web Store, paste your Deputy Pro key, and connect your agent.
Add the extension
Install Deputy from the Chrome Web Store. It works in Chrome or another Chromium browser on a desktop computer, Chrome 116 or later.
Deputy's setup page opens when the extension installs. To open it again, right-click the Deputy icon in the browser's toolbar and choose Options, or click the icon and then Setup & Pro.
Buy Pro and paste your key
Buy Deputy Pro on razin.ai/deputy. After checkout you get a license key that starts with dpro_. On the setup page, paste it under Deputy Pro and click Save.
The extension from the Chrome Web Store needs the key for everything. Without one, it reports no tabs to your agent, and every tool answers with how to get Pro.
Connect your agent
Add Deputy to your MCP client once. It needs Node.js 20 or later.
$claude mcp add deputy -- npx -y deputy-mcpCursor, Gemini CLI, VS Code, OpenCode and Claude Desktop take a config file instead: see Connect your agent. You don't start anything yourself: your client starts deputy-mcp when it starts, and the extension connects to it within a few seconds.
Ask
Open a page and tell your agent what to do there. It sees the page's forms as typed tools and fills one in a single call. See Forms as typed tools.
Check that it runs
The setup page's Status section shows each part:
| Row | What it says |
|---|---|
| Deputy Pro | active (with when it renews or ends), or what's wrong with the key |
| Deputy program | connected while deputy-mcp runs, with how many agents share it; otherwise "not running — it starts when your agent starts" |
| WebMCP in this browser | Whether Chromium's WebMCP is on. It's optional: without it, Deputy builds the forms itself, so everything still works |
| Running your agent's own JavaScript | Whether Chrome's "Allow User Scripts" switch is on for Deputy. Optional; only browser_eval needs it |
Click the Deputy icon on any website to see what that tab offers an agent. The popup lists the page's tools, each tagged:
- grafted: built by Deputy from the page.
- native: declared by the site itself.
- asks first: submitting it changes something, so your agent asks you first.
The pill at the top says whether the Deputy program is connected, starting or not connected.
From a terminal, while deputy-mcp runs:
curl http://127.0.0.1:7331/healthIt answers with JSON: whether the extension is connected (extensionConnected), how many other agents share the connection (peers), and how many tabs and tools Deputy sees.
Allow User Scripts (optional)
browser_eval runs JavaScript your agent supplies, through Chrome's User Scripts API. Chrome only allows that once you switch it on: open chrome://extensions (edge://extensions in Edge), click Details on Deputy, and turn on Allow User Scripts. Everything else works without it.
Next
- Choose what your agent may do, and whether Pro may send screenshots: Settings and environment.
- What Deputy reads and what leaves your computer: Privacy.