Skip to main content
Glama
efficjump

Local Dev Doctor MCP

by efficjump
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Local Dev Doctor MCP

No user-submitted related servers found.

    Related Servers

    • DevTwin MCP

      JaydeepDhamecha
      A
      license
      A
      quality
      B
      maintenance
      Provides AI coding agents with structured, evidence-based diagnostics about the local development environment, detecting tech stack, runtime mismatches, dependency state, services, ports, and Git status without exposing secrets or using network calls.
      10
      Apache 2.0

    • devenv-doctor-mcp

      Madiocre
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLM clients to inspect local dev environments—Docker container health, pnpm workspace integrity, and stuck process detection—without manual terminal copy-pasting.
      MIT

    • DevEnv Doctor MCP

      Madiocre
      A
      license
      A
      quality
      C
      maintenance
      Enables LLM clients to inspect local development environment, including Docker container health, pnpm workspace integrity, and stuck process diagnosis.
      4
      MIT

    • onboard-mcp

      developerpankajdixit
      A
      license
      A
      quality
      A
      maintenance
      Checks your local development environment for common issues like wrong Node version, missing Docker, missing git config, missing .env keys, and busy ports, and provides fixes.
      6
      8 npm
      1
      MIT

    • local-mcp-toolbox

      chriswayneh
      A
      license
      Not graded
      quality
      A
      maintenance
      A secure, local-first MCP server for read-only inspection and troubleshooting of development environments, exposing narrow, typed, auditable capabilities for repository inspection, log summarization, Docker review, and security scanning without granting unrestricted machine access.
      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/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct stage of the diagnosis pipeline: session creation/listing/retrieval, profile refresh, preflighting, probe preparation/execution, failure analysis, and report generation. No two tools appear to perform the same action, and the phase-specific descriptions make misselection unlikely.

    Naming Consistency5/5

    All tool names follow a consistent imperative verb_noun snake_case pattern such as start_diagnosis, execute_probe, and build_runbook_report. The object nouns are descriptive and align with the workflow, with only expected singular/plural variation.

    Tool Count5/5

    Nine tools is well within the ideal scope for a specialized diagnosis server. Each tool corresponds to one necessary step in the diagnostic lifecycle, so the count feels intentional rather than padded or sparse.

    Completeness5/5

    The tool surface covers the full diagnosis lifecycle: session setup, session retrieval, profile refresh, preflight checks, approved probe execution, failure analysis, and runbook report generation. There are no obvious dead ends or missing operations for the stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources