$ loading_
Diagnose broken FiveM servers or resources from configs, manifests, and logs.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "fivem-server-doctor-mcp" yet — see the docs or source repo.
Scan this FiveM server directory, including config files, resource manifests, and logs, and identify the most likely causes of the startup failure ranked by evidence strength.
A prioritized list of issues with likely causes, supporting evidence, and suggested actions.
Analyze this broken FiveM resource by checking its manifests, related configs, and logs, and explain which issue is most likely causing the resource to fail.
An evidence-backed diagnosis identifying the most suspicious issue and its likely impact.
With fix mode enabled, inspect the current FiveM server configs and resource files, then propose and apply low-risk text fixes where safe.
A list of applied or proposed low-risk text changes, with the issue each change addresses.
When a FiveM server fails to start or behaves unexpectedly, developers or DevOps engineers can use this tool to scan local configs, manifests, and logs to find the most likely causes. The findings are ranked by evidence so high-priority issues can be handled first.
When a FiveM resource cannot load or run correctly, the tool can diagnose it through resource manifests, configs, and logs to help determine where the problem lies. This reduces the need to manually inspect multiple files.
When the relevant option is enabled, the tool can not only suggest fixes but also apply low-risk text changes. This is useful for addressing clear, low-risk configuration-style problems first.
It is used to diagnose why a FiveM server or resource is broken or malfunctioning. It scans local configs, manifests, and logs, then returns ranked findings with evidence.
When the relevant capability is enabled, it can propose and apply low-risk text fixes. The provided information only confirms low-risk text changes; for more details, see the source repository.
Based on the description, it scans local config files, resource manifests, and logs. The provided information does not specify any broader inspection scope; see the source repository.
Diagnose Minecraft servers through plugin, log, configuration, and performance analysis.
Diagnose system issues, monitor resources, inspect logs, and test connectivity.
Scan remote MCP servers for protocol, security, and TLS issues.
Diagnose network and service issues using cURL timings and targeted recommendations.
Scan configured MCP servers locally and generate inventory with risk scores.
Diagnose infrastructure issues with ports, DNS, logs, system health, and SSL checks.