Summary: An MCP server that gives an AI agent read-only access to the Roblox Developer Forum, official creator docs, and the live engine API dump — no key or login required.
Search the DevForum (search_devforum) — full-text search with filters for category, tag, solved-only, min likes, date and ordering; pass up to 5 phrasings at once, merged and re-ranked toward solved/recent threads.
Check known bugs (search_bugs) — searches only bug-report categories (engine, Studio, cloud services, mobile, website, Creator Hub, purchasing, docs) to answer "is this a Roblox bug or my code?"
Read threads (get_thread, get_replies) — get a topic as Markdown with the accepted answer hoisted first and code blocks intact; page through long threads for buried answers.
Browse without a query (list_recent, list_categories) — latest or top topics per category/tag, plus the full category and tag slug index.
Search and read official docs (search_creator_docs) — score pages by content, then fetch a specific page in full by repo path or create.roblox.com URL.
Verify APIs before shipping (check_api_health) — batch-check up to 25 classes, members or code expressions for existence, correct casing, deprecation with replacements, security levels and yielding.
Look up engine signatures (get_engine_api) — properties, methods, events and callbacks for classes, enums, datatypes and Luau libraries, with types, security and thread safety; supports member narrowing and inheritance.
Track platform changes (get_whats_new, get_weekly_recap) — a recent-changes digest (Weekly Recap + release notes + announcements) and the full Weekly Recap archive by week offset or date.
Agent-friendly output — every tool is read-only, returns Markdown with source URLs, and respects a per-call max_tokens budget.
Configurable and portable — optional env vars for cache TTL, timeouts, retries, concurrency, docs scan depth, cache dir and alternate Discourse base URL; ships as a small native Rust binary or via npx.
Provides access to the Roblox Developer Forum and official creator docs, enabling searches of forum topics and bug reports, reading threads and replies, checking API health and engine API details, and retrieving recent Roblox platform changes and weekly recaps.
An MCP 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. A small native binary (Rust): starts instantly, uses ~6 MB of RAM.
claude mcp add roblox-devforum -- npx -y roblox-devforum-mcpdsh plugin --profile web add roblox-devforum-mcpAny other MCP client:
{
"mcpServers": {
"roblox-devforum": {
"command": "npx",
"args": ["-y", "roblox-devforum-mcp"]
}
}
}No Node.js? Download the binary for your system from the
latest release, or build it
with cargo install --git https://github.com/EL4CTEO/roblox-devforum-mcp, then use it directly:
claude mcp add roblox-devforum -- /path/to/roblox-devforum-mcpRelated MCP server: Chlorpromazine MCP Server
Tool | What it does |
| Search the forum. Filters for category, tag, solved-only, likes and date. Pass several phrasings to run them at once. |
| Search only the bug-report categories, so a hit means somebody reported the same symptom. |
| Read a topic as Markdown, accepted answer first, code blocks intact. |
| Page through a long thread. |
| Latest or top topics in a category or tag. |
| Every category and tag slug the filters accept. |
| Search the docs by page content; pass |
| Signatures, security levels and deprecations for classes, enums, datatypes and Luau libraries. |
| Check APIs before you ship: removed, deprecated, wrong case, security-gated, yielding. |
| Recent platform changes — for "this worked last week". |
| 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.
"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.
All optional.
Variable | Default | Purpose |
|
| Search cache lifetime, in seconds. |
|
| Per-request timeout. |
|
| Total time one request may spend, retries included. |
|
| Retries on 429 and 5xx. |
|
| Simultaneous requests to the DevForum. |
|
| Simultaneous requests to GitHub-hosted docs. |
|
| Doc pages scored per search. |
| OS temp dir | Where the API dump and docs index are cached. |
|
| Point at another Discourse instance. |
| — | npm only: run this binary instead of the bundled one. |
A bad value is ignored, with a note on stderr, and the default is used.
devforum.roblox.com (public Discourse API), Roblox/creator-docs, and the Roblox-Client-Tracker API dump.
Not affiliated with or endorsed by Roblox Corporation.
Needs Rust 1.99+.
cargo build --release # target/release/roblox-devforum-mcp
cargo test # offline unit and tool tests
npm run inspect # MCP Inspector against the release buildReleases: push a vX.Y.Z tag and CI builds every binary, publishes to npm and attaches the
binaries to the GitHub release. See CHANGELOG.md.
MIT
Batch-check Roblox APIs before you ship Luau that uses them. Pass entries like "Humanoid.MoveTo", "BodyVelocity", "Enum.Material.Neon", "task.wait" or "wait" and each is verified against the live API dump and the official docs: does it still exist, is it spelled with the right case, is it deprecated (with the official replacement where the docs give one), is it locked behind a security level normal scripts cannot use, and does it yield. Use this whenever you are about to write or review Roblox code — models often reproduce APIs that Roblox retired years ago.
Inputs: members (required), max_tokens.
Authoritative signature lookup from the live Roblox API dump: a class's properties, methods, events and callbacks with parameter types, security level, deprecation and thread safety. Use this to confirm a method exists, check whether it is deprecated or server-only, or find the right member name before writing Luau.
Inputs: name (required), filter, max_tokens, member_types, +1 more.
Fetch a page of replies from a DevForum topic in post order. Use after get_thread when the answer is buried further down a long thread.
Inputs: page, limit, topic, topic_id, +1 more.
Read a DevForum topic as Markdown: the original post plus the most useful replies, with the accepted answer hoisted to the top. Accepts a topic id or a full DevForum URL. Code blocks are preserved. Use get_replies to page through the rest.
Inputs: topic, topic_id, max_posts, max_tokens.
Read any Roblox Weekly Recap, current or historical. Roblox publishes one every Friday summarising what shipped that week: betas, engine updates, Marketplace and Studio changes. Use week to step back through the archive (0 = newest, 1 = the week before, …), before to jump to the recap covering a past date, or list to see the archive index. To find when a specific feature or regression landed, list the archive and read the recaps around that date.
Inputs: list, week, limit, before, +1 more.
A digest of recent Roblox platform changes: the official Weekly Recap, engine Release Notes, and Announcements. Use this when a game regressed for no obvious reason ("this worked last week"), when checking whether a Roblox update explains new behaviour, or when the user asks what is new on the platform. Returns the latest Weekly Recap body plus everything else published inside the time window.
Inputs: days, limit, max_tokens, include_recap_body.
List the DevForum category tree and the most-used tags. Call this when you are unsure which category or tag slug to pass to search_devforum, search_bugs, or list_recent.
Inputs: tag_limit, include_tags.
Browse a category or tag without a search query. Use release-notes / announcements to check whether a recent Roblox update explains a regression, or scripting-support to see what is breaking for others right now.
Inputs: tag, limit, period, listing, +2 more.
Search only the DevForum bug-report categories (engine, Studio, cloud services, mobile, website, Creator Hub, purchasing). Use this to answer "is this a known Roblox bug or is it my code?" — a hit means somebody reported the same symptom, with its category, last-activity date and whether a reply was marked as the solution. Roblox does not tag reports with a public triage state, so read the thread with get_thread to see whether staff actually answered.
Inputs: query (required), area, after, limit, +1 more.
Find and read pages from Roblox's official creator documentation (create.roblox.com/docs). Call with query to list matching pages, then call again with path from a result to read that page in full. Use this for intended behaviour, limits and quotas, and guide-level explanations — pair it with search_devforum for what actually happens in production.
Inputs: path, limit, query, max_tokens.
Full-text search across the Roblox Developer Forum. Use this first when a Roblox bug, error message, or engine behaviour needs community context: paste the literal error string (e.g. "502: API Services rejected request") or a symptom description. Results are re-ranked to favour solved and recent threads. Follow up with get_thread on the topic_id you want to read.
Inputs: query (required), tags, after, limit, +5 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 11 tools
Most tools target clearly distinct intents: official docs vs. DevForum search vs. bug reports vs. thread reading vs. API lookup vs. recap browsing. There are some overlaps — search_bugs is a constrained form of search_devforum, get_whats_new overlaps with get_weekly_recap and list_recent, and check_api_health overlaps with get_engine_api — but the descriptions make the intended boundaries fairly clear.
All tool names use snake_case and follow a predictable verb-first pattern: search_*, list_*, get_*, and check_*. The naming is consistent throughout and each name maps cleanly to a resource or action.
Eleven tools is well-scoped for a Roblox documentation/community/API research server. Each tool appears to earn its place, covering search, browsing, thread retrieval, API verification, and release tracking without excessive surface area.
The surface covers the apparent domain comprehensively: official docs search/read, DevForum category discovery, full-text and bug-specific search, thread and reply retrieval, recent browsing, API existence/signature checks, and weekly recap/what's-new history. No obvious lifecycle gap or dead end is apparent.
Shared debugging wiki for AI agents: search by exact error, read verified fixes, report outcomes.
Provide your AI coding tools with token-efficient access to up-to-date technical documentation for…
Collective memory for AI agents. One agent solves a bug — every agent gets the fix instantly.