Select a layout layer on a live web or Android UI, move it, and hand the edit to any MCP agent.
MCPpedia last refreshed this data
io.github.AntonChuraev99/layout-debug-mcp is an MCP server that select a layout layer on a live web or Android UI, move it, and hand the edit to any MCP agent. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 81/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"layout-debug": {
"env": {
"LD_TARGET_URL": "http://localhost:3000"
},
"args": [
"-y",
"layout-debug-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Select a layout layer on a live web or Android UI, move it, and hand the edit to any MCP agent.
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
npx -y 'layout-debug-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked layout-debug-mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in other
Private-by-default, local-first memory/context/task orchestrator for MCP apps and agents.
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
SQL for Android APK and DEX files: classes, methods, strings, references and smali.
System 1 decision models (Jev, Laya, Cua-S1) as brain for agents: Browser use, computer use, games and robotics
MCP Security Weekly
Get CVE alerts and security updates for io.github.AntonChuraev99/layout-debug-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Point at the element. Tell your agent what to change.
Stop describing UI to your AI agent in words. Alt+click any layer in your running page or Android app and type the change in its chat. Your agent (Claude Code, Codex, Cursor, Copilot…) gets the element's anchors, box and parents over MCP, edits the code and answers in the same chat while the frame refreshes with the result.
Need it 16 px lower? Drag it on the real screen first; the measured delta goes along.
Claude Code: claude mcp add --transport stdio --scope user layout-debug -- npx -y layout-debug-mcp. Other clients: Connect your MCP client.
20-second loop recorded from the real tool; the agent's side is a scripted MCP client, its wait sped up 2×. Watch the MP4 for full quality.
What the tool sees. It captures screenshots and the layout tree of the UI you point it at and hands them to the agent you connect. Don't run it against screens that show data you wouldn't paste into that agent.
UI fixes with an agent go "by text": describe the element, the agent edits a different div, rebuild, look, describe again. Half the time goes into explaining which element you mean.
layout-debug-mcp is a local window over your running UI. You pick the element on the picture, so there's nothing to explain. If you want it 16 px lower, you drag it and the real page (or the phone) moves, no rebuild. The agent gets measurements, not adjectives.
| Without | With layout-debug-mcp |
|---|---|
| Screenshot, circle the button, "the grey one under the price, no, the other one" | Alt+click the button and type the change in its chat |
| "Move it a bit lower" | Drag it 16 px; the real page moves |
The agent greps, edits the wrong div, you rebuild and look | The agent gets the element's anchors (test id, classes, file:line where available), box and offset 0, 16, and edits the right element |
| You check |