poco-mcp

# poco-mcp Small local stdio MCP server for live Unity Poco automation. The server exposes seven tools: - `observe`: compact visible UI snapshot with stable refs and locators; use `query` to narrow candidates and `include_world=true` for buildings and map HUDs - `tap`: click one explicit ref, locator, text, or normalized position; optionally wait for text or page scope evidence - `swipe`: scroll a view by direction and normalized anchor; observe again after each swipe to find an off-screen target - `wait`: wait for a text or node name to appear or disappear - `exists`: cheap remote Poco existence check - `input_text`: type into a focused input - `run_steps`: execute a previously verified sequence of stable selectors in one MCP call; page and text checks use Poco selectors rather than hierarchy dumps `observe` and `tap` return `timings_ms` for MCP-side latency. Model tokens and API cost must be recorded by the model host, not this local MCP. ## Install ```powershell pip install poco-mcp poco-mcp ``` ## Claude Code Skills The package includes the verified live-flow and script-export skills, but Claude Code discovers skills from the current project rather than from Python's site-packages. Install them once in the user's project: ```powershell cd <project-directory> poco-mcp-init ``` This creates `.claude/skills/live-script-builder` and `.claude/skills/poco-script-export`. Existing skills are left untouched. Use `poco-mcp-init --force` to update only the files managed by this package. For a source checkout, install the development extras before running tests: ```powershell pip install -e ".[dev]" pytest -q ``` ## Shareable Allure Report Install the optional reporting dependencies on the machine that executes generated regression scripts: ```powershell pip install -e ".[report]" ``` Install Allure 2 Commandline with `--single-file` support, or point the runner at an existing `allure.cmd`. Generate o…