MCP Tools Directory
← Browse integrations

Developer tools

FiveM MCP

Free account · sign-in required

Contact FiveM MCP

Loading secure sign-in…

Tools for autonomous AI agents

About this integration

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

Transport
stdio
Authentication
unknown
Initial setup
credentials
Runtime
unattended
Evidence
documented
Version
0.6.0
Package
fivem-mcp-server
Last compatibility test
Not independently tested

Connect your agent

fivem-mcp-server

Publisher README and npm manifest reviewed from hash-pinned captures. Eligibility is documented, not runtime-tested or independently security-audited. Publisher warns that RCON is administrative access, devcon may be unauthenticated, and the bridge is for development servers only.

Capabilities: FiveM server and client console automation, Console and log observation with wait assertions, Game-window input and screenshot automation, Development bridge operations

Connected profiles

Additional details

Registry identifier

io.github.ziyacivan/fivem-mcp

Source ↗ · Checked 2026-09-17
Published version

0.6.0

Source ↗ · Checked 2026-09-17
Metadata license

CC0-1.0; package licenses are separate

Source ↗ · Checked 2026-09-17
Package ecosystem

npm

Source ↗ · Checked 2026-09-17
Source artifact

fivem-mcp-server

Source ↗ · Checked 2026-09-20
Source manifest version

0.6.0

Source ↗ · Checked 2026-09-20
Unattended configuration

Publisher documentation describes a local stdio MCP process and agent-driven workflows that run commands, monitor logs, wait for assertions, and react without keyboard input. Documentation was reviewed; the package and integrations were not executed.

Source ↗ · Checked 2026-09-20
Authentication and prerequisites

Authentication is target-dependent rather than one uniform scheme: RCON commands require the configured FXServer rcon password, bridge calls can use a separate bridge token, server-info access needs no credentials, and the local devcon socket itself has no authentication. Setup therefore requires credentials for privileged target operations.

Source ↗ · Checked 2026-09-20
Connection configuration

The MCP client starts the npm executable as a local process and communicates over stdio; the process then connects to an administered FiveM environment using UDP RCON/getinfo, TCP devcon, local log access, and the optional development bridge as configured.

Source ↗ · Checked 2026-09-20
Review scope

Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.

Source ↗ · Checked 2026-09-20