What an MCP server is
The Model Context Protocol is an open standard for how an AI client talks to a system it does not own. Instead of producing text about that system, the client calls tools the system itself provides — and gets real data back rather than a guess.
For a FiveM server that means the client no longer works on a template but on your own data. Four things change with it.
- It sees what actually exists on your server — your items, your shops, your groups, not an example from a documentation page.
- It changes them in the same place you would change them in the admin panel. No second path opens up that drifts apart at the next update.
- It writes no code that somebody has to maintain afterwards. What it creates is a record, not a script.
- It works with your permissions. Access can never do more than the person who issued it is allowed to do.
The gap to an AI chat without MCP is therefore not one of degree. Without access you get a suggestion to type out yourself. With access you get a change to confirm.
What the RPFX MCP can do
The tool catalogue is kept deliberately small: nine tools, two of them dispatchers for reading and planning. Behind those sit more than 250 capabilities — a client that orients itself with describe_capabilities only ever fetches the ones it needs, instead of a catalogue that fills the whole context.
That covers, among other things:
- Economy: items with image, description and metadata, item types, recipes, crafting benches, bank accounts, and an overview of how much money is in circulation.
- Shops: assortment, prices, selling mode and ordering — for goods, vehicles, clothing and tattoos.
- Map content: blips, models, peds with their animation, doors, teleporters, interactive models, checkpoints, and whole map projects that deploy and roll back in one piece.
- Groups and jobs: members, wages, permissions through feature flags, custom jobs with their steps, side jobs and missions.
- Vehicles: stock, categories, licence plates, garages, and the export configuration for your own vehicle packs.
- World and events: weather plan, fire spawn points, contaminated zones, zombie zones, gang war zones and factions, farm areas, petrol stations.
- Looking things up instead of guessing: search across props, animations, particle effects and the framework's knowledge articles, plus road routes, place descriptions and spawn point suggestions.
- Checking after the fact: dedicated operations that report whether a new item has an image, whether a map entry is actually visible, and whether a group holds the permissions it needs.
What a given access really sees depends on its permissions: anything whose admin panel page is out of reach is not in the catalogue either.
The catalogue grows with the framework. The binding answer is always describe_capabilities on your own connection — this page is a description, not an interface guarantee.
Connecting
MCP access belongs to a server, not to an account: first there is a FiveM server in the portal, then an access for it, then the client.
- Connect the serverSign in to the portal, connect your FiveM server and start the rpfx-core resource on it. The admin panel opens up after that.
- Create an accessIn the admin panel, use the MCP icon in the header to create an access. The token is shown in clear text exactly once; the panel drops it straight into a ready-made snippet for your client.
- Connect a clientTake the snippet — a terminal command for Claude Code, a block in mcp_config.json for Antigravity, three fields for connector dialogs. RPFX then shows up in the tool list of your client.
claude mcp add --transport http rpfx https://data.rpfx.org/v1/mcp \
--header "Authorization: Bearer <token>"Clients with a connector dialog use OAuth in the browser instead, so there is no token to copy at all. Both routes end at the same address with the same permissions.
Without MCP the panel works exactly as before. The AI route is an offer, not a requirement, and it can be revoked at any time without anything on the server depending on it.
How this differs from the other FiveM MCP servers
Search for "FiveM MCP" and you mostly find two kinds of project, and both answer a different question than this page does.
The first serves documentation: the FiveM natives, the official docs pages and sometimes code samples are made searchable for an AI client. You still write the Lua yourself — the MCP makes sure the client names the right call with the right arguments. The second talks to the running process, usually over RCON: issue console commands, kick players, read the server status.
The RPFX MCP sits at a third place — not the documentation and not the console, but the content: the items, shops, groups and map entries the server is made of. That is possible because RPFX holds those as data rather than as code; a framework whose economy lives in Lua files would have nothing there to describe.
The three kinds do not exclude each other. If you write your own resources, a natives MCP alongside RPFX still earns its place — RPFX does not replace it.
What the access may and may not do
An access that can change a live roleplay server is a serious authority. Three things bound it, and none of them is a setting you can forget to switch on.
- Planning is separate from writingThe planning tools create nothing, they only note an intention. It takes an explicit apply_plan to carry a draft out — so you see everything the AI proposes in full before any of it takes effect.
- Permissions still applyEvery tool hangs off the same feature flag as the matching page in the admin panel. Access can never do more than the person who issued it is allowed to do, and tools outside those rights never appear in the catalogue in the first place.
- Player data stays lockedReading data that relates to individual players is switched off out of the box and has to be released by the server's leadership on purpose. Without that release the access sees the configuration of the server, not the people on it.
Application and database run in Germany at OVH, the backups also in Germany at Hetzner. What is processed in detail is set out in the privacy policy; the data processing agreement governs the relationship between RPFX and the server operator.