# FiveM Docs MCP server

> Search and read independent FiveM server and scripting guides with citation URLs.

- Listing: https://mcp.tc/i/fivem-docs
- Connect: use the server's own URL `https://fivemdocs.com/api/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Docs & Knowledge](https://mcp.tc/c/docs-knowledge)
- Vendor: Livvux
- Homepage: <https://fivemdocs.com/>

## About

Connects to the FiveM Docs site, an independent set of guides for FiveM server owners and developers. It covers txAdmin, frameworks such as QBCore, ESX and Qbox, Lua, JavaScript and C# scripting, server operations, performance and security. Two read-only tools search guides by keyword and fetch a guide's Markdown text with a citation URL.

The server is a hosted Streamable HTTP endpoint at https://fivemdocs.com/api/mcp. No sign-in or API key is needed. This is not official Cfx.re documentation.

## What it can do

- Search FiveM guides by short keywords
- Fetch a guide's Markdown/MDX text by ID
- Get citation URLs for returned guides
- Look up framework, txAdmin and scripting documentation

## Tools (3)

- `search`: Find public FiveM guides by short keywords; returns up to ten citable results. (read-only)
- `fetch`: Retrieve a guide's Markdown/MDX text and citation URL using an ID from search. (read-only)
- `lookup`: Read blip sprites, control IDs/default bindings, or ped names/hashes from the same imported data used on the website. (read-only)

## Example prompts

- "Search FiveM Docs for how to set up txAdmin recipes"
- "How do state bags work in FiveM? Cite the guide."
- "Find the FiveM docs on securing network events"
- "Fetch the guide on migrating from QBCore to Qbox"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http fivem-docs https://fivemdocs.com/api/mcp
```

2. Start Claude Code and type `/mcp`. **fivem-docs** should show as connected.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **FiveM Docs** and paste this URL:

```url
https://fivemdocs.com/api/mcp
```

3. Click **Add**. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=FiveM%20Docs&connectorUrl=https%3A%2F%2Ffivemdocs.com%2Fapi%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://fivemdocs.com/api/mcp` and click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://fivemdocs.com/api/mcp` as the server URL, then for authentication choose **No authentication**.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=fivem-docs&config=eyJ1cmwiOiJodHRwczovL2ZpdmVtZG9jcy5jb20vYXBpL21jcCJ9>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "fivem-docs": {
      "url": "https://fivemdocs.com/api/mcp"
    }
  }
}
```

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=fivem-docs&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Ffivemdocs.com%2Fapi%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"fivem-docs","type":"http","url":"https://fivemdocs.com/api/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "fivem-docs": {
      "type": "http",
      "url": "https://fivemdocs.com/api/mcp"
    }
  }
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "fivem-docs": {
      "serverUrl": "https://fivemdocs.com/api/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add fivem-docs --url https://fivemdocs.com/api/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.fivem-docs]
url = "https://fivemdocs.com/api/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http fivem-docs https://fivemdocs.com/api/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "fivem-docs": {
      "type": "http",
      "url": "https://fivemdocs.com/api/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://fivemdocs.com/api/mcp`.

## Recent changes

- 2026-10-25 11:42 UTC: 1 tool added. Server instructions changed. Source: automatic check. Worth a look: new server instructions. Added: lookup.
- 2026-10-18 19:24 UTC: Tracking started: 2 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/fivem-docs#history (Atom feed: https://mcp.tc/i/fivem-docs/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 1.0.0
- MCP protocol version: 2025-11-25
- Last checked: 2026-11-15 (reachable)
- Listed: 2026-10-18
- Updated: 2026-10-25

---
Source: https://mcp.tc/i/fivem-docs (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
