"Origin" matching MCP servers:

Just to be clear about the final JSON: the MCP server is named herdr-inbox, and it enables Claude Code agents in herdr to ask questions asynchronously without stalling, with all open questions answered from one popup and answers routed back to the asking agent.

Enables multiple AI agents to each run Google's full Chrome DevTools toolset in an isolated Chrome instance with saved logins, origin allowlists, reconnect recovery, and process cleanup. It also provides visibility into running browsers so stale sessions can be inspected or reaped.

Enables an AI agent to drive a real Chrome instance on a hidden Windows desktop, acting on accessibility element references instead of coordinates, with each session isolated on its own private desktop, profile, and ports. Credentials are typed into a masked popup and injected by an origin-bound, DPAPI-encrypted broker, so passwords never reach the model.

Connects selected Chrome tabs to ChatGPT through a private MCP connection so users can inspect pages, snapshot interactive elements, click, fill, select, scroll, navigate, and capture screenshots. Access stays limited to tabs the user explicitly enables, and each tab remains restricted to its current origin.

Enables an AI agent to read and operate the Chrome or Edge tabs you are already using — titles, URLs, text, HTML, screenshots, clicks, typing, scrolling, and tab management — via a browser extension and native messaging, without restarting the browser, switching profiles, or opening a debug port. It exposes these capabilities as 19 MCP tools, with access limited to explicitly shared tabs and hardened by per-tab, origin-bound grants plus domain allow/deny lists.

Enables running a stateless Model Context Protocol server over Streamable HTTP on Cloudflare Workers or any fetch-capable runtime, with signed sessions, origin checks, and JSON-RPC request handling. It lets developers define tools with JSON Schema validation and per-request context.

Enables coding agents to control the user's real Chrome or Firefox tabs, with their existing logins, to read pages, click, type, fill forms, take screenshots, inspect network traffic and run JavaScript. It works through a paired browser extension over a local WebSocket connection, so automation happens in the browser the user is actually looking at, including shadow DOM, cross-origin iframes, dialogs and single-page apps.

MCP server for local browser control via Chrome/Edge extension, enabling agents to open isolated tabs, observe pages, take screenshots, and interact with accessible controls using an existing browser profile. It is agent-agnostic, local-only, and supports safe session scoping with origin grants and sensitive-data blocking.