FiveM MCP Server

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

Packages and local setup

The published npm package is fivem-mcp-server, version 0.6.0. Its declared MCP transport is stdio.

The package declares FIVEM_HOST: Machine running the FiveM client (DevCon host). Default 127.0.0.1; FIVEM_CLIENT_DEVCON_PORT: Override the client devcon port (default: try 29200 then 29300); FIVEM_RCON_ADDRESS: FXServer game host:port for RCON/getinfo. Default :30120; FIVEM_RCON_PASSWORD: Matches rcon_password in server.cfg; required for server_command and the bridge; FIVEM_SERVER_LOG: Path to FXServer's redirected stdout (server.log); enables server-side read_console/wait_for_console (optional fallback transport for pre-0.5 bridges); FIVEM_MCPB_TOKEN: Matches mcpb_token on the server when the bridge resource is configured with one; FIVEM_EXECUTABLE: Path to FiveM.exe for the launch tool. Default %LOCALAPPDATA%\FiveM\FiveM.exe; FIVEM_CONSOLE_CAPACITY: Client console lines kept in the ring buffer. Default 5000; FIVEM_QUIET_MS: Consider client command output complete after this quiet period. Default 400; FIVEM_COMMAND_TIMEOUT_MS: Default max wait for client_command output. Default 5000; FIVEM_MCP_DEBUG: Set to 1 to trace devcon frames and RCON round-trips on stderr.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.6.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.