FiveM Unofficial MCP
Related Servers
Alternatives to FiveM Unofficial MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA focused MCP server for FiveM teams to scaffold resources, generate NUI templates, and perform safe file edits.1143 npm1MIT
- AlicenseBqualityCmaintenanceEnables writing, debugging and reviewing FiveM resources through read-only tools for installed-skill search and retrieval, task context composition, canonical template previews, source triage, manifest validation, resource inspection, official native lookup and resource planning. Includes an optional authenticated WebSocket bridge for realtime, resource-scoped telemetry from a development server.11MIT
- AlicenseBqualityDmaintenanceProvides comprehensive access to MCP documentation through structured guides, full-text search, and interactive development workflows for building servers and clients.343 npmMIT
- AlicenseBqualityDmaintenanceA unified development tool for RedM that provides access to RDR3 discoveries, framework documentation (VORP/RSGCore), native functions across 86+ namespaces, and database operations with smart context-aware loading.137MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to inspect, create, modify, and manage FiveM/RedM server resources, configuration, backups, and live runtime actions through a secure MCP interface.12MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to research game mods by searching documentation and definitions, inspecting dependencies and playsets, validating saved files with structural and Tiger checks, and preparing or editing mod content with preview and write controls. It also supports starting or previewing the game through a local stdio connection.8 npmGPL 3.0
TDQS
Scored across 43 tools
Most tools have clearly distinct resource+action targets, and the prefix namespacing (server_/resource_/game_/nui_/test_/performance_/knowledge_) makes the boundary obvious. A few pairs overlap in intent: server_get_status vs server_get_diagnostics (diagnostics is 'status plus errors'), resource_control vs dev_cycle (both refresh/restart), and nui_list vs resource_list, though the descriptions differentiate them.
Names are uniformly snake_case with a stable domain prefix for nearly every tool (server_, resource_, game_, nui_, test_, performance_, knowledge_). A handful of cross-cutting tools (db_query, lua_eval, client_get_logs, wait_for, dev_cycle) break the prefix pattern, and ordering varies (game_get_state vs game_spawn vs resource_list), but the scheme is still predictable.
43 tools is heavy for a single server, even though the domain (server ops, resource authoring, in-game testing, NUI automation, profiling, DB, docs) is genuinely broad. Several groups could be consolidated: three diagnostics tools, performance_get split from performance_get_resource, and generic one-offs like db_query and lua_eval could be folded in.
Coverage is strong end to end: resource CRUD plus deploy/control, server lifecycle and logs, game state/spawn/teleport/environment, NUI snapshot-act-eval, scenario testing, profiling and DB inspection. Obvious gaps remain in test scenario lifecycle (no list/update/delete for stored scenarios, only create/execute) and no file-level delete or patch for resources.