FiveM MCP Server

A comprehensive Model Context Protocol (MCP) server for FiveM (GTA5) development, built with Laravel. This server provides AI assistants with powerful tools and resources to help develop FiveM resources more efficiently.

Overview

The FiveM MCP Server enables seamless integration with AI coding assistants (Claude, ChatGPT, etc.) to provide:

• Native function lookups with client/server separation
• Event documentation for all frameworks
• Framework support for Standalone, ESX, QBCore, COX, and Prodigy Scripts (prp-bridge)
• Resource generation with customizable boilerplate
• Documentation search across FiveM, QBCore, and COX MySQL
• Code snippets and best practices for common patterns

Live Site

A live instance is available at: https://fivem-mcp.kingsoflossantos.com

This site includes interactive documentation, tool descriptions, and integration guides.

Quick Start

Installation

# Clone the repository
git clone https://github.com/yourusername/fivem-mcp.git
cd fivem-mcp

# Install dependencies
composer install
npm install

# Copy environment file and generate key
cp .env.example .env
php artisan key:generate

# Run database migrations
php artisan migrate

# Build frontend assets
npm run build

Running the Server

Live AI Assistants (Claude/Client):

{
  "servers": {
    "fivem": {
      "url": "https://fivem-mcp.kingsoflossantos.com/fivem",
      "type": "http"
    }
  }
}

Local Testing:

php artisan mcp:inspector fivem

Start the MCP Server:

php artisan mcp:start fivem

For AI Assistants (Claude/Cline): Configure in your AI client settings:

{
  "servers": {
    "fivem": {
      "command": "php",
      "args": ["/path/to/fivem-mcp/artisan", "mcp:start", "fivem"]
    }
  }
}

Tools

The MCP server includes 30 powerful tools organized by framework and execution side:

FiveM Core (7 tools)

• SearchFiveMDocs - Search FiveM, QBCore, and COX documentation
• GetNativeClientFunction - Look up client-side native functions (10 natives)
• GetNativeServerFunction - Look up server-side native functions (12 natives)
• GetEventClientReference - Client-side event reference (5 events)
• GetEventServerReference - Server-side event reference (4+ events)
• GenerateManifest - Generate fxmanifest.lua with framework support
• GenerateResourceBoilerplate - Complete resource scaffolding

QBCore Framework (9 tools)

• GetQBCoreServerFunction - QBCore server functions (13+ functions)
• GetQBCoreClientFunction - QBCore client functions (6 functions)
• GetQBCoreServerEventReference - QBCore server events (6 events)
• GetQBCoreClientEventReference - QBCore client events (6 events)
• GetQBCoreConfig - QBCore configuration reference
• GetQBCorePlayers - Player management functions
• GetQBCoreResourceList - Available QBCore resources
• GetQBCoreResourceReference - Resource-specific documentation
• GetQBCoreSharedData - Shared data (jobs, items, vehicles)

COX / ox_libs (10 tools)

• GetCOXFunction - OxMySQL database functions (8 functions)
• GetCOXEventReference - COX-specific events
• GetInventoryServerFunction - ox_inventory server functions (21 functions)
• GetInventoryClientFunction - ox_inventory client functions (8 functions)
• GetOxDoorlockClientFunction - ox_doorlock client API
• GetOxDoorlockServerFunction - ox_doorlock server API
• GetOxDoorlockServerEvent - ox_doorlock server events
• GetOxFuelClientFunction - ox_fuel client API
• GetOxFuelServerFunction - ox_fuel server API
• GetOxTargetClientFunction - ox_target client API

Prodigy Scripts / prp-bridge (4 tools)

• GetProdigyClientEventReference - prp-bridge client-side events (11 events across notifications, callbacks, allowlist, medical)
• GetProdigyServerEventReference - prp-bridge server-side events (8 events across framework, groups, medical, UniQueue)
• GetProdigyClientExport - prp-bridge client exports (allowlist, prop placer, ped interactions)
• GetProdigyServerExport - prp-bridge server exports (24 exports: cooldowns, allowlist, groups, UniQueue, sell shops, cases)

Project Structure

app/Mcp/
├── Tools/
│   ├── COX/
│   │   ├── Doorlock/
│   │   │   ├── Client/GetOxDoorlockClientFunction.php
│   │   │   └── Server/
│   │   │       ├── GetOxDoorlockServerFunction.php
│   │   │       └── GetOxDoorlockServerEvent.php
│   │   ├── Fuel/
│   │   │   ├── Client/GetOxFuelClientFunction.php
│   │   │   └── Server/GetOxFuelServerFunction.php
│   │   ├── Inventory/
│   │   │   ├── Server/GetInventoryServerFunction.php
│   │   │   └── Client/GetInventoryClientFunction.php
│   │   ├── MySQL/
│   │   │   ├── GetCOXFunction.php
│   │   │   └── GetCOXEventReference.php
│   │   └── Target/
│   │       └── Client/GetOxTargetClientFunction.php
│   ├── FiveM/
│   │   ├── Client/
│   │   │   ├── GetNativeClientFunction.php
│   │   │   └── GetEventClientReference.php
│   │   ├── Server/
│   │   │   ├── GetNativeServerFunction.php
│   │   │   └── GetEventServerReference.php
│   │   ├── GenerateManifest.php
│   │   ├── GenerateResourceBoilerplate.php
│   │   └── SearchFiveMDocs.php
│   ├── Prodigy/
│   │   ├── Client/
│   │   │   ├── GetProdigyClientEventReference.php
│   │   │   └── GetProdigyClientExport.php
│   │   └── Server/
│   │       ├── GetProdigyServerEventReference.php
│   │       └── GetProdigyServerExport.php
│   └── QBCore/
│       ├── Client/
│       │   ├── GetQBCoreClientFunction.php
│       │   └── GetQBCoreClientEventReference.php
│       ├── Server/
│       │   ├── GetQBCoreServerFunction.php
│       │   └── GetQBCoreServerEventReference.php
│       ├── GetQBCoreConfig.php
│       ├── GetQBCorePlayers.php
│       ├── GetQBCoreResourceList.php
│       ├── GetQBCoreResourceReference.php
│       └── GetQBCoreSharedData.php
├── Resources/
│   ├── CodeSnippets.php
│   ├── BestPractices.php
│   ├── FrameworkComparison.php
│   └── DatabaseQueries.php
├── Prompts/
│   ├── CreateNewResource.php
│   ├── DebugIssues.php
│   ├── OptimizePerformance.php
│   ├── ConvertLanguage.php
│   └── AddFrameworkIntegration.php
└── Servers/
    └── FiveMServer.php

Resources

MCP Resources provide read-only reference documentation:

1. Code Snippets - Common FiveM patterns in Lua and JavaScript
2. Best Practices - Performance optimization and security guidelines
3. Framework Comparison - Standalone vs ESX vs QBCore differences
4. Database Queries - COX MySQL examples and patterns

Prompts

Interactive prompts to guide AI assistants:

1. Create New Resource - Scaffold a complete FiveM resource
2. Debug Issues - Analyze and fix FiveM errors
3. Optimize Performance - Improve resource efficiency
4. Convert Language - Translate between Lua and JavaScript
5. Add Framework Integration - Migrate between frameworks

Testing

Run the test suite to ensure everything works:

# Run all tests
php artisan test

# Run specific test file
php artisan test tests/Feature/GetNativeClientFunctionToolTest.php

# Run with coverage report
php artisan test --coverage

Current Test Status: 181 tests passing ✅

Code Quality

This project follows PSR-12 coding standards and uses Laravel Pint for automatic formatting:

# Format all code
vendor/bin/pint

# Check formatting without fixing
vendor/bin/pint --test

Documentation

• FiveM Documentation
• FiveM Natives Reference
• QBCore Documentation
• COX MySQL Documentation
• Prodigy Scripts Documentation
• Laravel MCP Documentation
• Model Context Protocol

Architecture Notes

Client/Server Separation

All tools are organized by execution side (Client or Server) to ensure AI assistants provide appropriate code examples. For example:

• GetNativeClientFunction only contains client-side natives
• GetNativeServerFunction only contains server-side natives
• Events are similarly separated to avoid confusion

Framework Organization

Tools are grouped by framework (FiveM, QBCore, COX) to make discovery intuitive and keep documentation focused.

Response Format

All tool responses use consistent formatting with:

• Function/event signatures
• Parameter descriptions
• Return types
• Lua and JavaScript code examples
• Complete usage patterns

Contributing

To add new tools or improve existing ones:

1. Create a new tool class in app/Mcp/Tools/{Framework}/{Side}/
2. Implement the Tool interface
3. Add corresponding test file in tests/Feature/
4. Register in app/Mcp/Servers/FiveMServer.php
5. Run tests: php artisan test
6. Format code: vendor/bin/pint
7. Submit PR with description

License

MIT License - See LICENSE file for details

Support

For issues or questions:

• Review FiveM docs
• Open an issue on GitHub