Connect Coding Agents to WebMCP
Connect Codex, Claude Code, Gemini CLI, Pi, Hermes and 50 more coding agents to WebMCP with the AgentRQ Chrome extension and ACP Gateway.
Any coding agent that speaks the Agent Client Protocol can call the tools websites offer through WebMCP, in your own signed-in Chrome, without running in a browser itself. The AgentRQ Chrome extension shares a site's tools with an AgentRQ workspace, and the open-source ACP Gateway runs your agent and hands it that workspace's tools. Pick your agent below for a step-by-step guide.
What Is WebMCP?
WebMCP is a proposed web standard that lets a website offer tools to AI agents. The page registers named tools with the browser through document.modelContext, each with a description, a JSON Schema for its input, and a hint saying whether it only reads. An agent calls a tool directly and gets structured data back, instead of reading the screen and clicking. Our WebMCP explainer goes deeper.
On its own, a WebMCP tool can only be called by an agent inside the same browser tab. AgentRQ removes that limit.
How It Works
-
1.
The AgentRQ Chrome extension notices sites that register WebMCP tools, and you share one with a workspace.
-
2.
The ACP Gateway starts your agent and passes every session your workspace's MCP server, from
.mcp.json. -
3.
Through that server the agent gets
listSiteTools,getSiteToolDefinitionandcallSiteTool. -
4.
AgentRQ forwards each call to your Chrome, the extension runs it in the site's tab as you, and the result goes back to the agent.
Read-only tools run straight away. Anything else waits for your approval in the task: Allow once, Always allow that tool on that site, or Deny.
Claude Code can also skip the gateway: connected natively, as in the Claude Code guide, it gets the same site tools.
Guides by Agent
Each card opens that agent's step-by-step guide. The line under its name is how the ACP Gateway starts it.