RPScripts MCP server for FiveM developers

Connect Claude, ChatGPT, Cursor, VS Code or OpenCode to RPScripts. Search FiveM resources, check compatibility, validate Lua and server.cfg, generate manifests and jobs.

RPScripts runs a remote Model Context Protocol (MCP) server for FiveM development. Connect it to your AI assistant or code editor and it can search the RPScripts catalogue, check whether a resource fits your server, validate Lua code, manifests and server.cfg files, look up public servers, and create manifests and job resources. Signed in, it can also list your purchases, create download links and use the RPScripts AI script generator.

Server URL (Streamable HTTP)

https://rpscripts.net/mcp

No sign-in is needed for the public tools. Tools that act for your account ask you to sign in to RPScripts through OAuth the first time you use them. Your client opens the RPScripts login page, you approve the access, and your password or login code never passes through the client.

Connect in one step

Claude Code

claude mcp add --transport http rpscripts https://rpscripts.net/mcp

Cursor, Windsurf and other clients with an mcpServers file

mcp.json

{
  "mcpServers": {
    "rpscripts": { "url": "https://rpscripts.net/mcp" }
  }
}

Claude and ChatGPT: add a custom connector with the server URL above. Setup for every client, including VS Code and OpenCode, is in Connect a client.

What it can do

Tool	What it does	Sign-in
`search_products`	Search scripts, MLOs, server packs, vehicles and assets; filter by framework, category and price	No
`get_product`	Description, frameworks, price, categories and install requirements of one product	No
`list_categories`	Every shop category with its path and URL	No
`check_compatibility`	Does a product or your resource fit your framework, resources, artifact and OneSync?	No
`validate_resource`	Lua syntax, `fxmanifest.lua`, missing files, dependencies, framework API calls, security patterns	No
`validate_server_cfg`	Syntax, duplicate settings, start order, missing dependencies and exposed secrets in `server.cfg`	No
`generate_fxmanifest`	A valid `fxmanifest.lua` for Lua, JS, NUI, maps and vehicle data	No
`create_job`	A complete QBCore, Qbox or ESX job resource from the Jobs Creator	No
`search_docs`	RPScripts guides and the QBCore, Qbox, ESX and ox API reference	No
`lookup_server`	Public data of a FiveM server by join code or address	No
`list_purchases`	Your purchased products, files and download status	Yes
`get_download_url`	A personal, short-lived download link for a file you own	Yes
`generate_script`	Build or change a resource with the RPScripts AI generator, using your AI credits	Yes

Each tool, its inputs and an example request are in the tool reference.

Try these prompts

"Find a QBCore police job under $30 on RPScripts and check it against my server: qb-core, ox_lib, ox_inventory, oxmysql, artifact 17000."
"Validate this resource and fix what is broken" (attach your fxmanifest.lua and Lua files).
"Check my server.cfg for problems" (paste it; RPScripts never echoes secret values back).
"Create a mechanic job for Qbox with a garage and a boss menu."
"Show my RPScripts purchases and give me the download link for the newest one."

How the answers are made

The server only reports what it can show. Catalogue data comes from published RPScripts products; compatibility answers are supported, unsupported or unknown, each with its evidence: the catalogue listing, RPScripts Lab's static check of the download, the dependency's own fxmanifest.lua, or what you sent. Code checks are static: uploaded code is parsed, never run, and a clean result is not proof that a resource works on a live server.

Limits and privacy

120 requests per minute per IP address; code analysis 30 per minute; server lookups 30 per minute.
Requests up to 2 MB. server.cfg up to 256 KiB.
Downloads keep the website's rules: only products you own, 20 downloads per product per day, links valid for 5 minutes.
generate_script spends AI credits only after you approve it in your client. Pricing.
Configs and code you send are processed in memory and not stored, except generate_script projects, which are saved to your RPScripts AI workspace.

More on access and scopes: Sign-in and permissions.