Skip to main content
Glama
vincentvella

devloop

by vincentvella
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to devloop

Related Servers

  • VibeWatch

    krjordan
    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.
    4 npm
    3
    MIT

  • mcp-console-hub

    nano-step
    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.
    8 npm
    1
    MIT

  • AgentWatch

    mishanefedov
    A
    license
    Not graded
    quality
    A
    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
    11 npm
    14
    MIT

  • console-stream-mcp

    Topman-14
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI coding agents to access live console logs, errors, and network requests from web applications via a local WebSocket connection, without copying data to chat.
    7 npm
    18
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

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

ActivityActive
ResponsivenessResponsive

Resources