vincentvella/devloop
by Various
Browser control + dev-server logs on one correlated timeline — an MCP server with a headless (stdio) mode and an Electron cockpit. Built for AI agents.
MCP
vincentvella/devloop
Added 13 July 2026
Overview
An MCP server that correlates browser automation with dev-server logs on a single timeline. Offers a headless stdio mode for programmatic use and an Electron cockpit for visual debugging. Built for AI agents to interact with web development workflows.
Best for
Best for
Developers building AI agents that need to observe or control browser-based dev workflows.
Use cases
- Let AI agents control a browser and inspect live dev-server logs in sync
- Debug or replay browser interactions alongside backend output for end-to-end testing
- Provide a structured timeline of browser events and server logs for agent-driven analysis
Notes
An MCP server that correlates browser automation with dev-server logs on a single timeline. Offers a headless stdio mode for programmatic use and an Electron cockpit for visual debugging. Built for AI agents to interact with web development workflows.
0 stars on GitHub. Last updated 2026-07-13. Licensed MIT.
Use cases
- Let AI agents control a browser and inspect live dev-server logs in sync
- Debug or replay browser interactions alongside backend output for end-to-end testing
- Provide a structured timeline of browser events and server logs for agent-driven analysis
Pros
- Correlated timeline of browser state and server logs simplifies debugging
- Dual modes (headless and Electron cockpit) suit both automation and visual inspection
- Open source and written in TypeScript, easy to integrate into existing toolchains
Cons
- Zero GitHub stars indicates very early stage with limited community validation
- No evidence of production use or maintenance guarantees
- Requires running an Electron app for the cockpit, which may be heavy for headless-only setups
Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.
Pros
- Correlated timeline of browser state and server logs simplifies debugging
- Dual modes (headless and Electron cockpit) suit both automation and visual inspection
- Open source and written in TypeScript, easy to integrate into existing toolchains
Cons
- Zero GitHub stars indicates very early stage with limited community validation
- No evidence of production use or maintenance guarantees
- Requires running an Electron app for the cockpit, which may be heavy for headless-only setups
Get the free Developer’s Field Guide
A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.
Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.