AI Skill Report Card

Building Roblox GUIs with ForgeGUI

B+78·Nov 21, 2026·Source: Extension-page
14 / 15
Bash
# 1. Add ForgeGUI as an MCP server to Codex CLI codex mcp add forge-mcp --url https://forgegui.com/mcp # 2. Sign in via the link Codex prints, approve access in ForgeGUI # 3. Reconnect later if needed codex mcp login forge-mcp

Then start a new Codex session, invoke any ForgeGUI tool, and verify the connection on the ForgeGUI dashboard ("Check connection").

Recommendation▾
Add a troubleshooting example for Claude-specific MCP connection (currently all examples are Codex-centric despite mentioning Claude in description)
13 / 15

Progress:

  • Step 1: Connect Roblox account to ForgeGUI (dashboard shows connected username + publishing status)
  • Step 2: Connect AI client (Codex or Claude) to ForgeGUI via MCP
  • Step 3: Connect Roblox Studio (enable Studio's MCP server + Quick Connect)
  • Step 4: Start a new project and build/publish through the AI agent

Step 1: Connect Roblox Account

  • On forgegui.com, link the Roblox account that will own/publish the GUI projects.
  • Confirm "Publishing enabled" shows next to the connected username before proceeding.

Step 2: Connect AI Client via MCP

  • Use the client-specific CLI command to register ForgeGUI's MCP endpoint (https://forgegui.com/mcp).
  • For Codex: codex mcp add forge-mcp --url https://forgegui.com/mcp
  • Complete OAuth-style sign-in via the printed link — no API key required.
  • If the connection breaks or expires, re-auth with codex mcp login forge-mcp rather than re-adding.
  • Validate by running any ForgeGUI tool call in a fresh session, then confirm "Verified" status on the dashboard's connection checker.

Step 3: Connect Roblox Studio

  • Enable the MCP server inside Roblox Studio's settings.
  • Enable "Quick connect" so the CLI client (Codex) can reach Studio directly.
  • Follow the in-app "View Setup Instructions" link for exact menu paths (these can change with Studio updates).

Step 4: Build

  • Once all three connections show verified/enabled, open a new project in the AI client and issue natural-language build requests — ForgeGUI tools handle GUI generation and publishing back to the connected Roblox account.
Recommendation▾
Include a concrete example of an actual GUI build/publish request and expected output, not just connection troubleshooting
15 / 20

Example 1: Input: User says "I added forge-mcp to Codex but it still shows 'Not verified'." Output: Walk through: (1) confirm sign-in link was completed and access approved on forgegui.com, not just opened; (2) start an entirely new Codex session (stale sessions won't pick up new MCP auth); (3) invoke at least one ForgeGUI tool call to trigger verification; (4) click "Check connection" on the dashboard after the tool call completes.

Example 2: Input: User asks "Do I need a ForgeGUI API key for Codex?" Output: No — ForgeGUI uses OAuth-style sign-in through the link provided by codex mcp add/codex mcp login. No API key is needed for this flow.

Example 3: Input: User's Studio connection isn't picking up Quick Connect. Output: Verify Studio's built-in MCP server toggle is on (separate from ForgeGUI's own connection), then re-enable Quick Connect; this links Studio to the CLI client, not to ForgeGUI directly — ForgeGUI reaches Studio through the client's MCP session.

Recommendation▾
Clarify what happens if Roblox Studio version doesn't support MCP server (version/platform caveat missing)
  • Treat the three connections (Roblox account, MCP client, Studio) as independent and verify each one before troubleshooting "it doesn't work" broadly.
  • Always start a brand-new session after any MCP auth change — existing sessions cache the old connection state.
  • Use mcp login (not mcp add again) to refresh expired credentials; re-adding can duplicate server entries.
  • Check "Publishing enabled" status after connecting the Roblox account — a connected-but-not-enabled account will fail silently on publish.
  • Don't skip approving access on the ForgeGUI sign-in page — opening the link isn't enough, the user must explicitly approve.
  • Don't assume Studio connection follows automatically from MCP client connection — it's a separate enable step inside Studio itself.
  • Don't look for an API key field — this integration is link/OAuth-based only.
  • Don't test connection status in an old session; it won't reflect newly completed auth.
0
Grade B+AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
14/15
Workflow
13/15
Examples
15/20
Completeness
15/20
Format
14/15
Conciseness
14/15