The setup, to hand to an AI
The complete setup walkthrough is available as a plain text file: prerequisites, every step, plus the failure modes it usually gets stuck on. It is deliberately written so that it can be handed to an AI.
Give the file to Claude, ChatGPT, Antigravity or Gemini and add: "Read this and walk me through the setup step by step. Ask me where I am right now." After that you have someone who asks about your situation instead of making you work through a page.
It is generated from the same source the assistant in the admin panel draws on — so it cannot go out of date without anyone noticing.
The admin panel
The actual work happens in the admin panel: items, shops, recipes, vehicles, groups, jobs, map content, server settings. The same panel runs as a website and as an overlay in the game — including a map editor that lets you place positions exactly where your character is standing.
Every function hangs on its own feature flag, granted through groups. What someone may not do in the panel, they cannot do in-game or through an AI client either.
There is a knowledge article in the panel for every area — items and prices, shops, jobs, groups and rights, vehicles, the case file system, MCP access, building your own add-on. The assistant in the panel reads from the same collection and answers questions about it directly.
AI access via MCP
RPFX speaks the Model Context Protocol — the open standard through which AI clients operate external systems. You connect Claude, ChatGPT, Antigravity or any other MCP-capable client to your panel and describe what should happen on your server. The AI reads the existing data, plans the change and presents it to you.
Three things about this that get asked a lot:
- Nothing is written until you have explicitly confirmed it. Planning tools never change anything themselves.
- Every tool is tied to your account's feature flag. Access can never do more than the person who issued it is allowed to do.
- Access to data relating to individual players is switched off by default and has to be enabled explicitly by the server operator.
Without MCP access the panel works exactly as before — the AI route is an offer, not a requirement. The instructions for connecting, including ready-made snippets, are in the panel.
There is a page of its own about MCP access that goes into detail: what the protocol is, what the tool catalogue covers, how connecting works, and how RPFX differs from the other FiveM MCP servers.
Connecting your own resources
Your own scripts do not have to work around the framework: rpfx-core provides exports for server and client, plus in-game commands of your own. That way a third-party resource reads and writes the same data as the panel instead of building a second set beside it.
The complete catalogue of all exports is in the admin panel under Developer — stating whether an export runs on the server or the client, and with a generator for the matching call in Lua or TypeScript.
Data, rights and legal matters
A roleplay server administers data about players. What happens to it is not written up in a summary on this page but in the documents themselves — a second version of them could go out of date without anyone noticing.
Anyone connecting a server to RPFX processes their players' data in their own name; we do so on their behalf. The data processing agreement governs this, the privacy policy describes it in detail.