Skip to main content
Glama

Related Servers

Alternatives to SuperDev

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      A local-first MCP server that gives AI coding agents runtime visibility and AI-managed debug logging. It replaces blind print() debugging by turning runtime execution into causal chains, allowing agents to instantly locate bugs by finding missing .success events in Python and TypeScript code. Single binary with MCP, CLI, and HTTP interfaces.
      -
    • A
      license
      B
      quality
      A
      maintenance
      Local-first backend developer workspace exposing API debugging, SSH, database, workspace, and diagnostics tools to AI agents through a local MCP server
      72
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Gives AI coding agents (Claude Code, Cursor, etc.) unified, secure access to dev infrastructure (Vercel, GitHub, Supabase, Cloudflare, GCP) via a single MCP token.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      One MCP that turns Claude Code into your whole dev stack by swallowing other MCP servers, delegating to Codex & Gemini on your CLI subscriptions, remembering projects in a searchable knowledge graph, and carrying setup across sessions — secret-free by design.
      23
      4
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Production-grade MCP server that gives AI agents safe access to your local dev environment: filesystem, databases, processes, and OpenAPI specs.
      15
      43 npm
      3
      MIT

    TDQS

    C2.9/5.0

    Scored across 79 tools

    Disambiguation3/5

    Most tools target distinct resources or actions, and descriptions are generally detailed. However, there is meaningful overlap among log/diagnostic tools (follow_logs vs tail_logs, analyze_trace_logs vs summarize_error_window) and among config-edit/preview paths (upsert_project_config vs apply_config_change vs preview_config_change), which could cause an agent to pick the wrong one.

    Naming Consistency5/5

    Tool names follow a very consistent snake_case verb_noun or domain_verb pattern (browser_*, debug_*, list_*, upsert_*, preview_*). Even with 79 tools, the naming scheme is predictable and makes categories easy to identify.

    Tool Count1/5

    79 tools is an extreme mismatch for an MCP server surface. Even though the server covers many subdomains, the sheer count makes tool selection and discoverability very difficult for agents.

    Completeness4/5

    The tool set covers broad end-to-end workflows: projects, services, deployments, pipelines, browser debugging, code debugging, logs, test databases, and approvals. Minor gaps exist, such as no destructive delete operations for projects/services/pipelines and no advanced browser interactions beyond core actions.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues