deputy-mcp
v0.1.6
Published
Deputy's MCP bridge: Claude Code, Codex, Cursor and any MCP client use the pages in your browser as typed tools. Needs the Deputy Chrome extension; free to start, Deputy Pro adds 17 tools and hosted models.
Maintainers
Readme
deputy-mcp
The MCP bridge for Deputy: your MCP client talks to it over stdio, and it talks to the Deputy extension in your Chrome. The page never reaches the agent; the agent gets a typed tool for each form and makes one call.
# Claude Code: the plugin (adds /deputy:setup and a Deputy skill)
claude plugin marketplace add RazinAI/deputy && claude plugin install deputy@razin
# or a plain MCP server, for every project
claude mcp add --scope user deputy -- npx -y deputy-mcp
codex mcp add deputy -- npx -y deputy-mcp # CodexEvery other agent, from Gemini CLI and OpenCode to Cursor and Copilot: deputy.docs.razin.ai/docs/connecting.
Any other MCP client: run npx -y deputy-mcp as a stdio server.
Deputy is free to start: without a key your agent gets 10 tools. Deputy Pro adds the other 17 and hosted models; paste its license key on the extension's setup page. The open-source version is at github.com/zraisan/deputy.
Several clients can use the same browser at once. The first one to start owns the connection to
the extension on 127.0.0.1:7331; later ones share it, and take over if it exits. Each one works
in its own tab. Deputy enabled in more than one Chrome profile is fine too: each call goes to the
profile that has the tab. DEPUTY_PORT picks another port.
Your own model: Deputy can use an OpenRouter key of yours for
browser_ask and delegate_goal. Every Deputy process plans with its own key, so put it where
all of them read it, and no restart is needed:
mkdir -p ~/.config/deputy && echo 'OPENROUTER_API_KEY=sk-or-...' >> ~/.config/deputy/envOPENROUTER_MODEL there picks the model. The same variables in the environment win over the
file; DEPUTY_CONFIG moves the file.
License: PolyForm Shield 1.0.0.
