Weppy Roblox MCP

Weppy Roblox MCP bridges Claude to a running Roblox Studio session, letting you script, build, and test without leaving the chat. It's a proper two-way integration: the agent can spawn instances, write Lua, modify terrain, and trigger playtests, then read back results. The install script handles the Roblox plugin and MCP server in one go, which is rare for game engine integrations. I'd reach for this when prototyping game mechanics or batch-generating similar objects. Ask Claude to create a dozen platformer obstacles with varying jump heights, and it'll script them, place them in the workspace, and run a playtest to check collision. The feedback loop is tight: you see changes in Studio immediately, and the agent can query the scene graph to make informed next steps. It's particularly strong for repetitive tasks like populating a world with NPCs or generating loot tables as ModuleScripts. The quirks are real. You need Roblox Studio open and the Weppy plugin running before Claude can do anything. If Studio crashes or you close the session, the MCP server loses its connection and you'll need to restart both. The plugin communicates over localhost, so firewall rules matter. Documentation assumes you're comfortable with Roblox's object model; if you don't know what a Part versus a MeshPart is, you'll spend time clarifying in prompts. Playtest automation is the standout feature. You can ask Claude to run a test, wait for specific events (player touched a checkpoint, health dropped below 50), then adjust scripts based on what happened. It's not a substitute for proper QA, but it's excellent for sanity-checking logic changes. This isn't for casual Roblox tinkerers. If you're just learning Studio, the abstraction layer will confuse more than it helps. But for developers building systems or iterating on mechanics, it's a genuine productivity tool. The fact it works with Claude Desktop, Code, and Cursor means you can stay in your preferred environment. Just expect to babysit the Studio connection.