Skip to main content
Glama
fivem-server-doctor-mcp

fivem-server-doctor-mcp

by mkcrw

FiveM Server Doctor MCP

Local MCP server for Claude Desktop, Codex, and other MCP clients that answers one question:

Why is my FiveM server or resource broken?

fivem-server-doctor-mcp reads local txAdmin/FiveM files over stdio, scans server.cfg, resource folders, manifests, and recent logs, then returns ranked findings with exact evidence. It can propose narrow text-file fixes and can apply only generated low-risk fixes when writes are explicitly enabled.

Maintained by FiveMX. Sponsor link: fivemx.com.

What It Detects

  • Missing resource folders referenced by ensure or start.

  • Resource folders missing fxmanifest.lua or __resource.lua.

  • Common fxmanifest.lua problems: missing fx_version, missing game, missing listed files, missing dependencies.

  • txAdmin/FiveM log patterns: missing resources, malformed manifests, missing dependency hints, port bind failures, missing license keys, database connection hints, yarn/webpack/module install errors.

  • Secrets in output are masked, including license keys, DB URLs/passwords, tokens, and connection strings.

The scanner parses manifests as text. It never executes Lua from a resource.

Related MCP server: WSAI FixCenter

Install

pnpm add -g fivem-server-doctor-mcp

Or run it without a global install:

npx -y fivem-server-doctor-mcp --server-cfg /path/to/server.cfg --resources /path/to/resources

CLI Options

fivem-server-doctor-mcp \
  --txdata /path/to/txData/default \
  --server-cfg /path/to/server.cfg \
  --resources /path/to/resources

Optional txAdmin status check:

TXHOST_API_TOKEN=... fivem-server-doctor-mcp \
  --txadmin-url http://127.0.0.1:40120 \
  --txadmin-token-env TXHOST_API_TOKEN

Writes are disabled by default. Enable generated low-risk patch application only for the launched process:

FIVEM_DOCTOR_ALLOW_WRITE=1 fivem-server-doctor-mcp --server-cfg ./server.cfg --resources ./resources

Codex Setup

codex mcp add fivem-doctor -- npx -y fivem-server-doctor-mcp \
  --server-cfg /path/to/server.cfg \
  --resources /path/to/resources \
  --txdata /path/to/txData/default

Then ask Codex:

Use fivem-doctor to run doctor_scan and explain why my FiveM server is not starting.

Claude Desktop Setup

Add this to your Claude Desktop MCP config:

{
  "mcpServers": {
    "fivem-doctor": {
      "command": "npx",
      "args": [
        "-y",
        "fivem-server-doctor-mcp",
        "--server-cfg",
        "/path/to/server.cfg",
        "--resources",
        "/path/to/resources",
        "--txdata",
        "/path/to/txData/default"
      ]
    }
  }
}

For write-enabled local patching, add an env block:

{
  "mcpServers": {
    "fivem-doctor": {
      "command": "npx",
      "args": ["-y", "fivem-server-doctor-mcp", "--server-cfg", "/path/to/server.cfg", "--resources", "/path/to/resources"],
      "env": {
        "FIVEM_DOCTOR_ALLOW_WRITE": "1"
      }
    }
  }
}

MCP Interface

Tools:

  • doctor_scan: scans configured status, logs, server.cfg, resources, and manifests.

  • resource_inspect: inspects one resource folder and manifest.

  • propose_fixes: returns generated fix candidates.

  • apply_fix: applies one generated fix only when writes are enabled, the target hash matches, the path is under configured roots, and the fix risk is low.

Resources:

  • fivem://status

  • fivem://server-cfg

  • fivem://logs/recent

  • fivem://resources

  • fivem://resources/{name}/manifest

Prompts:

  • diagnose_fivem_startup

  • review_new_resource_install

  • explain_txadmin_log_error

Safety Model

  • No private txAdmin UI scraping.

  • No browser sessions, cookies, or CSRF-protected routes.

  • No RCON, restart, stop, ban, or live server control tools in v1.

  • No arbitrary file writes.

  • apply_fix only writes generated low-risk changes for server.cfg, fxmanifest.lua, or __resource.lua style text fixes under configured roots.

  • Existing files are backed up into .fivem-doctor-backups/ before replacement.

Development

pnpm install
pnpm build
pnpm test

The test suite uses fixture-based node:test coverage and starts a real stdio MCP client against the built server.

Docs

License

MIT

Available Tools

4 tools
apply_fixApply Generated FixA

Applies one generated low-risk fix only when writes are enabled, the file hash still matches, and the target path is under a configured root.

Inputs: fixId (required), expectedHash.

doctor_scanRun FiveM Server Doctor ScanA

Scans txAdmin status/logs, server.cfg, resources, manifests, dependencies, and returns ranked findings.

Inputs: no named parameters.

propose_fixesPropose Safe Text FixesA

Returns exact low-risk fix candidates generated from the current scan.

Inputs: no named parameters.

resource_inspectInspect FiveM ResourceA

Inspects one resource folder, manifest, dependencies, and related file evidence.

Inputs: name (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      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.
      10
      MIT
    • 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
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to diagnose broken XAMPP/WAMP localhost stacks by inspecting real machine state — running processes, listening ports, HTTP probes, and Apache/MySQL error logs — to pinpoint port conflicts, startup crashes, unclean-shutdown damage, and zombie processes with plain-English explanations. All diagnostics are read-only, so agents can safely answer questions like why Apache won't start or why localhost refuses to connect instead of guessing.
      4
      MIT