Roblox Mcp

Created By
hope10263 months ago
Connect AI coding agents to a live Roblox Studio session. Create and edit scripts, instances, terrain, lighting, assets, audio, and animation with natural language.
Overview

What is Roblox MCP?

Roblox MCP connects AI coding agents to a live Roblox Studio session.

Instead of only generating code snippets, tools like Claude, Cursor, Codex, and Gemini can directly perform real actions inside Studio: create and edit scripts, manage instances and properties, generate terrain, adjust lighting, insert assets, and more.

Roblox MCP Demo

Features

  • Direct Studio control: execute changes instantly inside Roblox Studio
  • Scripts and instances: create, edit, move, rename, and delete with natural language
  • Properties and hierarchy: inspect and update the DataModel without manual clicking
  • Terrain and lighting: generate terrain, tune atmosphere, and adjust environment settings
  • Asset workflows: search, insert, and configure assets from prompts
  • Audio and animation: control sounds, animations, and effects directly in Studio
  • Full-project context: mirror Studio to local files with Sync for multi-file edits
  • Multi-client support: works with Claude Code, Cursor, Codex CLI, Gemini CLI, and other MCP-compatible clients

Sync

Sync helps AI understand your Roblox project across multiple files, not just one script at a time.

Sync Workflow

  • Basic: Studio -> Local one-way sync
  • Pro: bidirectional sync, advanced workflows, and richer project context

Roblox Explorer

Browse your synced Studio hierarchy directly in VSCode.

Roblox Explorer

GitHub Repository

Quick Install

npx -y @weppy/roblox-mcp

Server Config

{
  "mcpServers": {
    "roblox-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@weppy/roblox-mcp"
      ]
    }
  }
}
Project Info
Created At
3 months ago
Updated At
2 months ago
Author Name
hope1026
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Alloy

2 days ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

12 hours ago
Crevio

a day ago