Live Cube
3 × 3Current Scramble
No scramble yet.
Scramble starts from solved and resets solving moves to 0.Move History
Control Panel
Cube Size
Actions
Move Controls
Algorithm Input
Standard notation only. All actions share one sequential queue. Reset and size changes wait for earlier actions.Try asking your AI agent
- “Scramble the 3×3 cube.”
- “Show me the current cube state.”
- “Execute R U R' U'.”
- “Reset the cube.”
- “Switch to a 2×2 cube and scramble it.”
- “Check whether the cube is solved.”
- “Apply the sexy move six times.”
From solved, (R U R' U') × 6 returns to solved. Submit the expanded sequence, not parentheses or “× 6”.
WebMCP Tool Inspector
Agent Activity
Last 50 eventsStructured calls, not simulated clicks. UI, WebMCP, and System events are labeled separately.
How WebMCP works
- The page exposes structured Rubik's Cube tools.
- An AI agent discovers the available tools.
- The agent calls the tools with structured arguments.
- CubeEngine changes the application state.
- The UI immediately reflects the same state.
AI Agent Human
↓ ↓
WebMCP Tools UI Controls
└───────────┬────────────┘
CubeController
Shared Queue
↓
CubeEngine
↓
Cube State
↓
3D UI
Agent and human use the same application capability layer. No DOM guessing, backend, MCP server, SSE, or stdio. WebMCP runs in the browser page context through document.modelContext.
Face arrays use row-major order, viewed directly from outside each face. Values are original sticker colors: U = White, D = Yellow, L = Orange, R = Red, F = Green, B = Blue. State commits at the start of each turn; the visual transition then completes before the next queued move.
Browser support is experimental. If file URLs cannot access WebMCP in your browser, serve this unchanged file from an allowed localhost or HTTPS static origin. Human controls work without WebMCP.