roblox-devforum-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | Raises the GitHub rate limit for the docs file listing. | |
| DEVFORUM_BASE_URL | No | Point at another Discourse instance. | https://devforum.roblox.com |
| DEVFORUM_CACHE_DIR | No | Where the API dump and docs index are cached. | OS temp dir |
| DEVFORUM_CACHE_TTL | No | Search cache lifetime, in seconds. | 300 |
| DEVFORUM_DOCS_SCAN | No | Doc pages scored per search. | 14 |
| DEVFORUM_TIMEOUT_MS | No | Per-request timeout. | 12000 |
| DEVFORUM_CONCURRENCY | No | Simultaneous requests to the DevForum. | 4 |
| DEVFORUM_MAX_RETRIES | No | Retries on 429 and 5xx. | 3 |
| DEVFORUM_CDN_CONCURRENCY | No | Simultaneous requests to GitHub-hosted docs. | 8 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_devforumA | 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. |
| search_bugsA | 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. |
| get_threadA | 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. |
| get_repliesA | 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. |
| list_recentA | 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. |
| list_categoriesA | 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. |
| search_creator_docsA | Find and read pages from Roblox's official creator documentation (create.roblox.com/docs). Call with |
| check_api_healthA | 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. |
| get_engine_apiA | 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. |
| get_weekly_recapA | 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 |
| get_whats_newA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
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.