LaunchRepoDefinition
The Model Context Protocol (MCP) is an open standard for connecting AI agents to tools and data. An MCP server is a small program that lists what it can do — navigate, click, read a page, query a database — and the agent calls those tools as needed. Servers are registered in the agent’s configuration, typically as a command to start plus arguments.
Chrome DevTools MCP is the server that exposes a Chrome instance as tools. It is what makes a terminal agent a browser agent.
Why it matters for a directory launch
Without an MCP browser server a coding agent can only read and write files; it cannot fill a directory form. The server is also the boundary of trust: it controls the connected browser, so which Chrome it attaches to and how it is started decide what the agent can reach.
How LaunchRepo handles it
The repository documents a generic MCP server entry for chrome-devtools-mcp with --autoConnect (existing Chrome 144+) or --browserUrl (dedicated profile on a local port); where that entry goes depends on the agent — Claude Code, Codex and Cursor each have their own configuration location, described on their pages here. Node and npm are needed for npx; a tested package version should be pinned after setup. A running server process alone proves nothing until a visible tab moves.
See the term in the repository
LaunchRepo is 346 directory playbooks, a product context file and a submission tracker your own agent runs. Pay €99.98 once; use it for every product you own.
See pricing