fivem-server-doctor-mcp
Provides diagnostics for FiveM servers by scanning server.cfg, resource manifests, and logs to identify issues such as missing resources, malformed manifests, and common configuration errors, with the ability to propose and apply low-risk fixes.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@fivem-server-doctor-mcpdiagnose why my FiveM server won't start"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
ensureorstart.Resource folders missing
fxmanifest.luaor__resource.lua.Common
fxmanifest.luaproblems: missingfx_version, missinggame, 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: mcp-doctor
Install
pnpm add -g fivem-server-doctor-mcpOr run it without a global install:
npx -y fivem-server-doctor-mcp --server-cfg /path/to/server.cfg --resources /path/to/resourcesCLI Options
fivem-server-doctor-mcp \
--txdata /path/to/txData/default \
--server-cfg /path/to/server.cfg \
--resources /path/to/resourcesOptional txAdmin status check:
TXHOST_API_TOKEN=... fivem-server-doctor-mcp \
--txadmin-url http://127.0.0.1:40120 \
--txadmin-token-env TXHOST_API_TOKENWrites 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 ./resourcesCodex 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/defaultThen 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://statusfivem://server-cfgfivem://logs/recentfivem://resourcesfivem://resources/{name}/manifest
Prompts:
diagnose_fivem_startupreview_new_resource_installexplain_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_fixonly writes generated low-risk changes forserver.cfg,fxmanifest.lua, or__resource.luastyle text fixes under configured roots.Existing files are backed up into
.fivem-doctor-backups/before replacement.
Development
pnpm install
pnpm build
pnpm testThe test suite uses fixture-based node:test coverage and starts a real stdio MCP client against the built server.
Docs
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mkcrw/fivem-server-doctor-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server