fivem-server-doctor-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| txdata | No | Path to txData/default directory (optional) | |
| resources | Yes | Path to resources directory | |
| server-cfg | Yes | Path to server.cfg | |
| txadmin-url | No | URL of txAdmin (optional) | |
| TXHOST_API_TOKEN | No | The txAdmin API token (optional, used when txadmin-token-env is set to TXHOST_API_TOKEN) | |
| txadmin-token-env | No | Name of environment variable containing txAdmin API token (optional) | |
| FIVEM_DOCTOR_ALLOW_WRITE | No | Set to '1' to enable write operations (optional) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| doctor_scanA | Scans txAdmin status/logs, server.cfg, resources, manifests, dependencies, and returns ranked findings. |
| resource_inspectA | Inspects one resource folder, manifest, dependencies, and related file evidence. |
| propose_fixesA | Returns exact low-risk fix candidates generated from the current scan. |
| apply_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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| diagnose_fivem_startup | Guide an assistant through a startup failure diagnosis using doctor_scan first. |
| review_new_resource_install | Inspect a newly installed resource before server restart. |
| explain_txadmin_log_error | Explain a txAdmin/FiveM log error and connect it to local evidence. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| status | Optional txAdmin /host/status response, redacted. |
| server-cfg | Configured server.cfg content with secrets masked. |
| recent-logs | Recent .log files below txData, newest first, with secrets masked. |
| resources | Discovered resource folders and manifest paths. |
TDQS
Scored across 4 tools
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.
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.
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.
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.