devlooplisted

# Drive Devloop via mcporter [Devloop](https://github.com/vincentvella/devloop) puts a **browser** and your **dev server** on one timestamped timeline, so a browser error and the backend log from the same moment sit side by side. It exposes that as MCP tools: start a dev server, drive a browser (navigate / click / type / snapshot / screenshot), capture logs + network, `diagnose` what's broken, and `repro` a flow — plus native iOS/Android. When the Devloop MCP server is connected to this agent directly, just call the tools. **When it isn't — but you have a shell — use [mcporter](https://mcporter.sh) to call the same tools as commands.** ## Setup (once per machine) Run one shared, long-running Devloop and point mcporter at it: ```sh # Start a headless daemon (one shared instance on :7333). Use npx if devloop-mcp isn't installed. devloop-mcp daemon & # or: npx -y devloop-mcp daemon & # Sanity-check + discover tools (use --schema to see every tool's signature): npx mcporter list --allow-http --http-url http://localhost:7333/mcp --name devloop --schema ``` If spawning a process per call is fine and you'd rather not run a daemon, point mcporter at stdio instead: `npx mcporter list --stdio "npx -y devloop-mcp" --name devloop`. > `--allow-http` is required because the localhost URL is cleartext. Exact flags can vary by mcporter > version — `npx mcporter --help` is authoritative. ## Calling tools ```sh M='npx mcporter call --allow-http --http-url http://localhos