Skip to main content
Glama
README.md
<img src="https://raw.githubusercontent.com/EL4CTEO/roblox-devforum-mcp/main/assets/devforum.png" alt="Roblox Developer Forum" width="440">

# roblox-devforum-mcp

An [MCP](https://modelcontextprotocol.io) server that gives an AI coding agent the **Roblox
Developer Forum** and the **official creator docs**.

When your agent hits a Roblox bug, it can check whether Roblox already has it triaged, read the
accepted answer, and confirm the API before writing Luau.

No API key, no login, no setup.

## Install

```bash
claude mcp add roblox-devforum -- npx -y roblox-devforum-mcp
```

[DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness):

```bash
dsh plugin --profile web add roblox-devforum-mcp
```

Any other MCP client:

```json
{
  "mcpServers": {
    "roblox-devforum": {
      "command": "npx",
      "args": ["-y", "roblox-devforum-mcp"]
    }
  }
}
```

## Tools

| Tool | What it does |
| --- | --- |
| `search_devforum` | Search the forum. Filters for category, tag, solved-only, likes and date. Pass several phrasings to run them at once. |
| `search_bugs` | Search only the bug-report categories, so a hit means somebody reported the same symptom. |
| `get_thread` | Read a topic as Markdown, accepted answer first, code blocks intact. |
| `get_replies` | Page through a long thread. |
| `list_recent` | Latest or top topics in a category or tag. |
| `list_categories` | Every category and tag slug the filters accept. |
| `search_creator_docs` | Search the docs by page content; pass `path` to read a page in full. |
| `get_engine_api` | Signatures, security levels and deprecations from the live API dump. |
| `check_api_health` | Check APIs before you ship: removed, deprecated, security-gated, yielding. |
| `get_whats_new` | Recent platform changes — for "this worked last week". |
| `get_weekly_recap` | Any Roblox Weekly Recap, current or historical. |

Every tool is read-only, returns Markdown with source URLs, and stays inside a token budget.

`[answered]` beside a result means a reply was marked as the solution — by whoever opened the
thread, not by Roblox. Roblox does not publish a triage state, so read the thread to see
whether staff replied.

## Example

> *"My DataStore:SetAsync keeps failing with `502: API Services rejected request`. Is this on
> Roblox's end?"*

The agent runs `search_bugs` on the error text, `get_thread` on the best hit, then
`check_api_health` before touching your code.

## Configuration

All optional.

| Variable | Default | Purpose |
| --- | --- | --- |
| `DEVFORUM_CACHE_TTL` | `300` | Search cache lifetime, in seconds. |
| `DEVFORUM_TIMEOUT_MS` | `12000` | Per-request timeout. |
| `DEVFORUM_DEADLINE_MS` | `24000` | Total time one request may spend, retries included. |
| `DEVFORUM_MAX_RETRIES` | `3` | Retries on 429 and 5xx. |
| `DEVFORUM_CONCURRENCY` | `4` | Simultaneous requests to the DevForum. |
| `DEVFORUM_CDN_CONCURRENCY` | `8` | Simultaneous requests to GitHub-hosted docs. |
| `DEVFORUM_DOCS_SCAN` | `14` | Doc pages scored per search. |
| `DEVFORUM_CACHE_DIR` | OS temp dir | Where the API dump and docs index are cached. |
| `DEVFORUM_BASE_URL` | `https://devforum.roblox.com` | Point at another Discourse instance. |

A bad value is ignored, with a note on stderr, and the default is used.

## Data sources

[devforum.roblox.com](https://devforum.roblox.com) (public Discourse API),
[Roblox/creator-docs](https://github.com/Roblox/creator-docs), and the
[Roblox-Client-Tracker](https://github.com/MaximumADHD/Roblox-Client-Tracker) API dump.

Not affiliated with or endorsed by Roblox Corporation.

## Development

```bash
npm install && npm run build
npm test          # offline unit and server tests
npm run inspect   # MCP Inspector against the built server
```

## License

MIT

TDQS

A4.2/5.0

Scored across 11 tools

Disambiguation4/5

Most tools map cleanly to a distinct action and resource: search vs get vs list vs check. The boundary is slightly blurry between get_whats_new and get_weekly_recap (both concern recaps) and between check_api_health and get_engine_api (both query API metadata), but the descriptions are specific enough to guide most choices.

Naming Consistency5/5

Tool names follow a consistent verb_noun pattern: search_*, get_*, list_*, check_*. There are no mixed casing conventions or vague verbs, making the set predictable and easy to navigate.

Tool Count5/5

Eleven tools is well-scoped for a developer-support server covering forum search and reading, bug investigation, platform changelogs, official docs, and live API metadata. Each tool has a clear role in that workflow.

Completeness5/5

The tool surface covers the full research loop: discover categories, search forum/bug/doc content, read threads with paging, check recent platform changes and historical recaps, and verify API usage. No significant dead ends or missing lifecycle steps are apparent.

Maintenance

ActivityMaintained
ResponsivenessNo issues