Skip to main content
Glama

Related Servers

Alternatives to devloop

Related Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    Monitors development commands and exposes terminal output to Claude in real-time, allowing AI assistants to see errors, logs, and stack traces without copy-pasting.
    10 npm
    3
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Streams browser DevTools console, network, storage, and performance data to your IDE's AI agent for real-time debugging and analysis.
    11 npm
    1
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables coding agents to drive, inspect, and debug paired web and Expo apps by running registered actions, reading app state, inspecting network calls and errors, and capturing pixel-exact panel screenshots.
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    A 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 s
    8 npm
    16
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Lets 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 npm
    ISC
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents such as Cursor and Claude Desktop to read a running debugger's captured console logs and network sessions, inspect full request/response payloads, diagnose crashes and failed API calls, and trigger React Native reloads or the developer menu.
    495 npm
    MIT

TDQS

A4.2/5.0

Scored across 46 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count3/5

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.

Completeness4/5

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.

Maintenance

ActivityNo data
ResponsivenessOutdated data