The atlas, within reach
Your editor.
Our reference.
Better answers.
Give your AI the context your code deserves. Connect the RedM knowledge base through the Model Context Protocol.
Set up your connectionHTTP TRANSPORT / REDM KNOWLEDGE BASE
The same sources you browse.
Available to the tools you build with.
Real signatures.
Fewer guesses.
Look up native names, hashes, parameters, and return types from the reference.
The gotchas
come with it.
Linked community findings and native warnings help surface the details that matter.
Describe the goal.
Find the source.
Semantic search connects behavior questions to native and framework documentation.
Make the connection
A small config.
A deeper reference.
Choose your client, add the server, then ask a question. Each game has its own endpoint.
If your client requests authorization, follow its sign-in prompt. Client support for MCP can vary by version.
Open your MCP configuration
Add this server to .vscode/mcp.json in your project. For all projects, run MCP: Open User Configuration from the command palette. Merge the entry into the top-level servers object.
{
"servers": {
"redm-atlas": {
"type": "http",
"url": "https://redm-mcp.fivem.no/mcp"
}
}
}Connect, then ask with context
Start the server from the MCP server list and enable its tools in agent chat. Ask your AI to use the RedM reference for its answer.
Start a conversation
Good questions.
Grounded answers.
Try these prompts in your connected editor. They are starting points, not pre-generated answers.
Find the RedM native for spawning a horse. Explain its parameters and cleanup requirements.
How do I add an item to a player’s VORP inventory? Look up the current documentation.
Find community gotchas for the natives used in this resource.