weppy-roblox-mcp-guide

Use when controlling Roblox Studio through WEPPY Roblox MCP, choosing MCP tool actions, selecting among multiple connected Studio targets, creating or checking UI Studio interfaces, running playtests, inspecting logs, or verifying direct Studio workflows.

Jump to install

Repository: hope1026/weppy-roblox-mcp
Last source activity: August 27, 2026 at 06:02
Detected SKILL.md language: English
Stars: 60
Forks: 9

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/hope1026/weppy-roblox-mcp --skill weppy-roblox-mcp-guide

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

6 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

WEPPY Roblox MCP Guide

Overview

Use this skill to operate Roblox Studio through WEPPY Roblox MCP with the right tool/action sequence. Keep exact action and parameter lookup in references so the main workflow stays small.

Workflow

Check connection, tier, and connected Studio targets before mutating Studio. Use Basic-safe status actions first when available.

If more than one Studio target is connected, read references/multi-studio-routing.md, select one target, and keep its selector on related calls.

Choose the narrowest MCP action that matches the request. Read references/mcp-actions.md for exact action names, params, tier, route, and aliases.

For UI work, run the UI Studio loop in references/ui-studio.md instead of ad hoc GUI mutation.

For play mode, test scripts, logs, or dashboard reports, use references/playtest.md.

Prefer purpose-built tools over execute_luau. Use arbitrary Luau only when no typed action covers the request.

After mutating Studio, verify with a readback action, preview/check, logs, or playtest output depending on the workflow.

References

references/mcp-actions.md: generated MCP tool/action/parameter reference.

references/multi-studio-routing.md: deterministic target selection and selector precedence.

references/ui-studio.md: UI Studio design brief, create/update, preview, and Design Check loop.

references/playtest.md: playtest controls, automated test runner, logs, and screenshot limitations.

Guardrails

Do not invent Roblox asset IDs. Use user-provided IDs or an explicit accepted asset search result.

Do not call Edit-mode screenshot capture while a playtest is active.

Do not present Design Check suggestions as mandatory failures.

Do not expose raw action counts in user-facing marketing copy.