FiveM MCP for Grok

io.github.ziyacivan/fivem-mcp

Build, run and live-test FiveM servers with AI agents: RCON, DevCon, window control, mcpb bridge.

client:Grok transport:stdio runtime:npm

Install FiveM MCP in Grok

.mcp.json (in your project root)

FIVEM_HOST

FIVEM_CLIENT_DEVCON_PORT

FIVEM_RCON_ADDRESS

FIVEM_RCON_PASSWORD

FIVEM_SERVER_LOG

FIVEM_MCPB_TOKEN

FIVEM_EXECUTABLE

FIVEM_CONSOLE_CAPACITY

FIVEM_QUIET_MS

FIVEM_COMMAND_TIMEOUT_MS

FIVEM_MCP_DEBUG

Held in this page only — never stored, logged, or sent anywhere but back to your screen.

{
  "mcpServers": {
    "fivem-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "fivem-mcp-server"
      ],
      "env": {
        "FIVEM_HOST": "<FIVEM_HOST>",
        "FIVEM_CLIENT_DEVCON_PORT": "<FIVEM_CLIENT_DEVCON_PORT>",
        "FIVEM_RCON_ADDRESS": "<FIVEM_RCON_ADDRESS>",
        "FIVEM_RCON_PASSWORD": "<FIVEM_RCON_PASSWORD>",
        "FIVEM_SERVER_LOG": "<FIVEM_SERVER_LOG>",
        "FIVEM_MCPB_TOKEN": "<FIVEM_MCPB_TOKEN>",
        "FIVEM_EXECUTABLE": "<FIVEM_EXECUTABLE>",
        "FIVEM_CONSOLE_CAPACITY": "<FIVEM_CONSOLE_CAPACITY>",
        "FIVEM_QUIET_MS": "<FIVEM_QUIET_MS>",
        "FIVEM_COMMAND_TIMEOUT_MS": "<FIVEM_COMMAND_TIMEOUT_MS>",
        "FIVEM_MCP_DEBUG": "<FIVEM_MCP_DEBUG>"
      }
    }
  }
}

Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs

FiveM MCP in other clients

FiveM MCP MCP server