Skip to main content
Glama
mkcrw

fivem-server-doctor-mcp

by mkcrw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to fivem-server-doctor-mcp

No user-submitted related servers found.

    Related Servers

    • WSAI FixCenter by Whytcard-Swiss-AI

      WSAI FixCenterofficial

      Whytcard-Swiss-AI
      A
      license
      Not graded
      quality
      B
      maintenance
      Evidence-first MCP server for diagnosing problems with hooks, plugins, skills and configuration, returning ranked probable causes and reviewable fixes without modifying the workspace.
      MIT

    • dolu_fivem_mcp

      DoluTattoo
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables local FiveM development by letting an AI assistant execute JavaScript/Lua on the server or client, automate NUI interactions, capture game screenshots, manage resources, and run repeatable tests with screenshot evidence.
      4
      MIT

    • 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

    • TaskBounty Check

      eliottreich
      A
      license
      A
      quality
      C
      maintenance
      Local-only GitHub Actions and CI maintenance scanner for AI-built apps. Exposes scan, explanation, and fix-planning tools to MCP clients; modifies nothing and makes no outbound requests by default.
      3
      51 npm
      2
      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

    A3.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct responsibility: scanning the whole server, inspecting a specific resource, proposing fixes, and applying a single fix. There is no overlap or ambiguity in their purposes.

    Naming Consistency3/5

    Tool names use a two-word underscore pattern, but the verb/noun order is inconsistent: doctor_scan and resource_inspect are object-first, while propose_fixes and apply_fix are verb-first. This mix is still readable but not perfectly predictable.

    Tool Count5/5

    Four tools form a tight, well-scoped workflow for diagnosing and fixing FiveM servers. Each tool adds a necessary stage in the process, and there is no bloat.

    Completeness4/5

    The scan → inspect → propose → apply lifecycle is complete for the core server-doctor functionality. A minor gap is the lack of a revert or validation step after applying a fix, but it can be worked around.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources