redm-mcp

io.github.Cmoen11由 GitHub 帳號 Cmoen11 發布v0.1.0更新於 Oct 25, 2026

RedM / RDR3 docs MCP server: native lookups, semantic search, VORP, RSGCore, oxmysql.

已驗證Streamable HTTP可網頁執行知識與記憶開發者工具

概覽

AI 產生的概覽

面向 RedM / RDR3 文件的託管 MCP 伺服器,讓助理查詢原生函式、搜尋文件並閱讀框架參考。

可以做什麼
依雜湊或名稱精確查詢 RedM 原生函式,並依行為或概念搜尋,例如傳送玩家或生成馬匹。在原始文件檔案中進行正規表示式或字面檢索,包括行人、武器、動畫、道具與音訊庫等大型社群資料表。列出命名空間與分類、瀏覽文件路徑,並取得文件的完整 Markdown 內容。涵蓋 VORP、RSGCore 與 oxmysql 的框架文件。
適用情境
適合助理處理 RedM 或 RDR3 腳本時使用,需要準確的原生函式簽章、框架參考或社群雜湊資料,而不是猜測參數與語意。
執行需求
透過 HTTP 連線的遠端 MCP 端點,無需本機安裝,也無需身分驗證。僅支援 stdio 的用戶端需要 mcp-remote 之類的代理。需要能連線至該託管端點。
安裝前請注意
伺服器為託管且專有,原始碼未公開。請求與使用計數會傳送給營運方,統計端點據稱僅含中繼資料。清單宣告需要 OAuth,而 README 稱無需身分驗證,連線前應確認實際驗證方式。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 redm-mcp,將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.Cmoen11%2Fredm-mcp/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

{
  "mcpServers": {
    "redm": {
      "type": "http",
      "url": "https://redm-mcp.fivem.no/mcp"
    }
  }
}

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.

[Install in VS Code] [Install in VS Code Insiders] [Add to Cursor]

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:

lua
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

ToolUse
lookup_nativeExact lookup by hash or name. O(1). Use for Citizen.InvokeNative(0x...) or SCREAMING_SNAKE_CASE names.
semantic_searchSearch by behavior/concept ("teleport player", "spawn horse").
grep_docsRegex/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_namespacesList categories and namespaces.
browseList document paths under a category/namespace.
get_documentFetch 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

bash
claude mcp add --transport http redm-mcp https://redm-mcp.fivem.no/mcp

Or edit ~/.claude.json manually:

json
{  "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):

json
{  "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):

json
{  "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:

json
{  "servers": {    "redm-mcp": {      "type": "http",      "url": "https://redm-mcp.fivem.no/mcp"    }  }}

Zed

~/.config/zed/settings.json:

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-remote as a proxy

Verify it works

  1. curl https://redm-mcp.fivem.no/health → {"ok":true}
  2. curl https://redm-mcp.fivem.no/ingest-status → shows version and last ingested timestamp
  3. In your client: ask the agent to look up 0x09C28F828EE674FA — should return BOOST_PLAYER_HORSE_SPEED_FOR_TIME

Endpoints

PathAuthPurpose
POST /mcpnoMCP protocol
GET /healthnoLiveness
GET /ingest-statusno{ current, last, ingestedAt, upToDate }
GET /statsnoUsage stats (tool counters, durations, breakdowns). Metadata only — no queries or secrets stored.
GET /dashboardnoHTML 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:

來源:README.md,提交 905f8e2

工具

0
該伺服器需要登入,因此 SourceWeft 無法在沒有帳號的情況下讀取其工具,也未收錄。已連接帳號所能看到的內容可能因帳號及其權限而異。

版本歷史

1
  1. v0.1.0最新Sep 16, 2026

評分

已滿足適用檢查項的 75%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。