devloop
Related Servers
Alternatives to devloop
- AlicenseNot gradedqualityCmaintenanceAn MCP Server for Chrome DevTools, following the Chrome DevTools Protocol. Integrates with Claude Desktop and Claude Code.312MIT
- AlicenseAqualityAmaintenanceEnables interaction with iOS simulators by providing tools to inspect UI elements, control UI interactions, and manage simulators through natural language commands.174,519 npm2,193MIT
- AlicenseAqualityAmaintenanceEnables direct browser control via Chrome DevTools Protocol, supporting navigation, interaction, content extraction, and screenshots through a single MCP tool.1363MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI to control iOS simulators through the MCP protocol. Supports device management, UI automation, and network interception including screenshot capture, text input, and HTTP request mocking.-
- AlicenseBqualityAmaintenanceEnables controlling a local Chrome browser via MCP tools, using a Chrome extension and WebSocket broker for browser automation.3010 npm1MIT
- AlicenseBqualityAmaintenanceUse your signed-in Chrome through a local MCP server and companion extension. Supports tabs, navigation, forms, screenshots, and page reading, with a deny-all domain allowlist. Install: npx -y mcp-browser-extension@latest.22611 npm6MIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceMonitors development commands and exposes terminal output to Claude in real-time, allowing AI assistants to see errors, logs, and stack traces without copy-pasting.2 npm3MIT
- AlicenseNot gradedqualityDmaintenanceStreams browser DevTools console, network, storage, and performance data to your IDE's AI agent for real-time debugging and analysis.6 npm1MIT
- AlicenseNot gradedqualityCmaintenanceA terminal live-tail and a browser dashboard — one process, one event stream, served from localhost. Unified timeline across Claude Code, Codex, Gemini CLI, Cursor, Hermes, and OpenClaw. Token + cost accounting, compaction + anomaly detection, hybrid search, SVG call graphs, monaco-style diff attribution, agent-aware replay ("what would the agent say if I edited the prompt?"), policy editor, MCP s8 npm16MIT
- AlicenseNot gradedqualityAmaintenanceLets AI coding tools drive the real Chrome browser you already have open, so they can read and act on logged-in pages with real clicks, typing, navigation, screenshots, and network or storage inspection. Everything runs locally over stdio with no remote-debugging port, so nothing leaves your machine.1 npmISC
- AlicenseNot gradedqualityAmaintenanceLets AI coding tools drive the real, already-logged-in Chrome browser over local stdio—snapshotting and reading pages, clicking, typing, managing tabs, capturing screenshots, and inspecting network, console, storage, and cookies—without opening a remote-debugging port. It installs as a Chrome extension plus native-messaging bridge, so agents work in the user's authenticated sessions while passing bot detection.1 npmISC
- AlicenseNot gradedqualityNot gradedmaintenanceEnables Claude Code to control a real browser for navigating, clicking, typing, capturing screenshots, running multi-step E2E tests, assertions, visual regression, and session recording from the terminal.106 npmMIT
TDQS
Scored across 46 tools
Tools are grouped by clear prefixes and each description explicitly distinguishes it from neighboring tools, e.g. browser_snapshot vs browser_screenshot and get_logs vs get_network. A few pairs require careful reading—screenshot/snapshot and export_bundle/export_har are easy to mix up—but no two tools truly do the same job.
All tool names follow a consistent lowercase snake_case verb_noun pattern: browser_*, pane_*, dev_*, project_*, native_*, ext_*, plus get_*/clear_*/export_*. Standalone verbs like diagnose and repro are slightly different but still fit the command-oriented style, so the overall convention is predictable.
46 tools is heavy and well beyond the typical 3-15 range, which can overwhelm an agent. However, the server covers several distinct subsystems—browser automation, panes, logs, dev server, projects, native, and extensions—and each subsystem is fairly tightly scoped, so the count is large but not unjustified.
Core workflows are well covered: dev server start/stop/status, project registry, pane lifecycle, browser automation, log triage/export, native build/open/close, and extension install/toggle/remove. Minor gaps exist—no cookie/header manipulation and no separate project update—but project_add's replace semantics and browser_clear_storage provide reasonable workarounds.