redm-mcp
Enables AI agents to look up RedM/RDR3 native hashes, search documentation semantically, and access framework docs and community data for accurate coding assistance.
README
redm-mcp — RedM / RDR3 docs MCP server
Model Context Protocol (MCP) server for RedM / RDR3: native lookups (hash ↔ name), semantic search, framework docs (VORP, RSGCore, oxmysql), and the rdr3_discoveries community data (peds, weapons, animations, AI flags, props, audio banks). Gives AI coding agents (Claude Code, Cursor, Claude Desktop, VS Code Copilot, Zed, …) exact answers instead of guesses.
Runs as a hosted HTTP-transport MCP at https://redm-mcp.fivem.no/mcp — no local install, no auth, just point your client at it.
This repository contains only installation/usage docs and serves as the issue tracker. The server source code is proprietary and not distributed. The hosted endpoint is free to use.
Why
When an agent reads RedM code it typically encounters:
Citizen.InvokeNative(0x09C28F828EE674FA, player, 1.5, 5000)
Without a lookup, the agent guesses at parameters and semantics. With this server:
lookup_native({ hash: "0x09C28F828EE674FA" })
→ BOOST_PLAYER_HORSE_SPEED_FOR_TIME(player Player, speedBoost float, duration int)
The server advertises its own usage via MCP instructions — no skill or extra client config needed.
Tools
| Tool | Use |
|---|---|
lookup_native |
Exact lookup by hash or name. O(1). Use for Citizen.InvokeNative(0x...) or SCREAMING_SNAKE_CASE names. |
semantic_search |
Search by behavior/concept ("teleport player", "spawn horse"). |
grep_docs |
Regex/literal grep across raw doc files. Required for the large rdr3_discoveries data tables (audio_banks, ingameanims, …) which are only preview-indexed in embeddings. |
list_namespaces |
List categories and namespaces. |
browse |
List document paths under a category/namespace. |
get_document |
Fetch full markdown for a doc path. |
Client setup
All clients connect to https://redm-mcp.fivem.no/mcp. No authentication required.
VS Code and Cursor users: click an install badge above for one-click setup. For everything else, copy-paste the config below — also available as ready-made files in examples/.
Claude Code
claude mcp add --transport http redm-mcp https://redm-mcp.fivem.no/mcp
Or edit ~/.claude.json manually:
{
"mcpServers": {
"redm-mcp": {
"type": "http",
"url": "https://redm-mcp.fivem.no/mcp"
}
}
}
Cursor
Edit ~/.cursor/mcp.json (or .cursor/mcp.json in a project root):
{
"mcpServers": {
"redm-mcp": {
"url": "https://redm-mcp.fivem.no/mcp"
}
}
}
Restart Cursor. Check Settings → MCP for green status.
Claude Desktop
Claude Desktop doesn't support HTTP MCP directly — use mcp-remote as a proxy. Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"redm-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://redm-mcp.fivem.no/mcp"
]
}
}
}
Restart Claude Desktop.
VS Code (Copilot / Continue)
.vscode/mcp.json in a project root:
{
"servers": {
"redm-mcp": {
"type": "http",
"url": "https://redm-mcp.fivem.no/mcp"
}
}
}
Zed
~/.config/zed/settings.json:
{
"context_servers": {
"redm-mcp": {
"command": {
"path": "npx",
"args": [
"-y",
"mcp-remote",
"https://redm-mcp.fivem.no/mcp"
]
}
}
}
}
Other clients (generic)
- HTTP transport clients: point to
https://redm-mcp.fivem.no/mcp - stdio-only clients: use
mcp-remoteas a proxy
Verify it works
curl https://redm-mcp.fivem.no/health→{"ok":true}curl https://redm-mcp.fivem.no/ingest-status→ shows version and last ingested timestamp- In your client: ask the agent to look up
0x09C28F828EE674FA— should returnBOOST_PLAYER_HORSE_SPEED_FOR_TIME
Endpoints
| Path | Auth | Purpose |
|---|---|---|
POST /mcp |
no | MCP protocol |
GET /health |
no | Liveness |
GET /ingest-status |
no | { current, last, ingestedAt, upToDate } |
GET /stats |
no | Usage stats (tool counters, durations, breakdowns). Metadata only — no queries or secrets stored. |
GET /dashboard |
no | HTML dashboard over /stats. |
Example prompts
See examples/prompts.md for things to try once installed (native lookups, behavior searches, framework / inventory questions, debugging).
Issues / feedback
Bug, missing docs, incorrect native lookups, requests for new tools? Open an issue.
Doc sources
Indexed upstreams:
- femga/rdr3_discoveries — community ped/weapon/anim/prop hashes, AI flags, enums
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。