What it does
Layout Debug lets you select an element on a running web page or Android app, adjust it, and send the change to an MCP agent. You Alt+click a layer, optionally drag or resize it, and type the requested change in that element's chat. The agent receives the element's anchors (test id, id, class string, and file and line where available), its box, parent chain, and a measured delta of your live edits. It then edits the code and replies in the same chat while the frame refreshes. On Android, Jetpack Compose layers are identified by their file and line from the compiler, and overrides apply on the device without a Gradle build.
It suits cases where describing an element in words keeps pointing the agent at the wrong one, or where a small position or size change is easier to make by dragging than by explaining. Tailwind class strings give agents useful search anchors in web projects. A shimmer covers the element while the agent works, and an inbox shows each request as Queued, Agent editing, Done or Error. The interface is available in English and Russian. Window, server and MCP process run locally, with no cloud component; only anonymous usage counts are sent, and one variable turns them off.
Setup means adding the server to an MCP client such as Claude Code, Codex, Cursor or VS Code, which requires Node.js. Asking the agent to open the window starts a local server and opens it in the browser, first with a bundled demo page until you set your own target URL. Web use needs a page served by your dev server. Android use needs adb on the PATH and a debug build with the on-device agent. Source lines for web elements appear only if your build writes data-source-loc; otherwise the agent locates the element by test id, id and class string.
Limitations and requirements
Requires Node.js 22.12 or later (20.19 also works), an MCP-capable client, and a current browser such as Chrome, Edge or Firefox for the window. Android use requires adb in PATH and an app built in debug mode with the on-device agent. Web source lines require data-source-loc in the build. The publisher warns that the tool captures screenshots and layout trees and sends them to the connected agent, so do not run it against screens showing data you would not paste into that agent. Anonymous usage counts are sent unless disabled with the telemetry variable.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
Layout Debug
Select a layout layer on a live web or Android UI, move it, and hand the edit to any MCP agent.
v0.3.0As shown on registry.modelcontextprotocol.io when we last read it