← Index

FiveM MCP

io.github.ziyacivan/fivem-mcpv0.6.0Other

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

The current version, v0.6.0, was published to the official MCP registry on 2026-09-04. It is distributed as fivem-mcp-server on npm, filed under Other by this index, and declares 11 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using FiveM MCP in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
REVIEWstatus: PARTIALfresh until 2026-10-27 01:12 UTC
screened 2026-09-03tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidence“No malicious instructions”via static_description

Limits of this verdict
  • - Semantic screen only - the deterministic conformance probe has not run on this server
  • - Confidence is reported but not yet calibrated (v1)
  • - Screen reads the tool description, not the live behavior
  • - advisory
  • - registry description only no input schema
  • - screen model 8b
  • - Still current: the description we screened is unchanged, re-checked against the registry
  • - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Test a description on the public screen → It is a separate check from the verdict above, so the two can differ.

That verdict was true at screening time (snapshot 2026-10-20).

Contracts can change after screening, with no version bump. The gate pins FiveM MCP’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Cite this record

People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.

Markdown
[Independent trust record for FiveM MCP](https://mcpindex.ai/server/io-github-ziyacivan-fivem-mcp) - screening verdict, registry provenance, and contract drift monitoring.
HTML
<a href="https://mcpindex.ai/server/io-github-ziyacivan-fivem-mcp">Independent trust record for FiveM MCP</a> - screening verdict, registry provenance, and contract drift monitoring.
Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown
[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-ziyacivan-fivem-mcp)](https://mcpindex.ai/server/io-github-ziyacivan-fivem-mcp)
HTML
<a href="https://mcpindex.ai/server/io-github-ziyacivan-fivem-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-ziyacivan-fivem-mcp" alt="mcpindex verdict" height="20" /></a>
Environment variables
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 <FIVEM_HOST>:30120

FIVEM_RCON_PASSWORD
secret

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
secret

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

MCP quality score · maturity, not trust · methodology
freshness
24
completeness
15
installability
25
documentation
15
stability
5
Alternatives in Other