PoC Recorder MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POC_RECORDER_MCP_FPS | No | Frames per second for the recording. | 15 |
| POC_RECORDER_MCP_WIDTH | No | Viewport width in pixels. | 1440 |
| POC_RECORDER_MCP_HEIGHT | No | Viewport height in pixels. | 900 |
| POC_RECORDER_MCP_SHOW_HUD | No | Whether to show HUD step captions (true/false). | true |
| POC_RECORDER_MCP_LOG_LEVEL | No | Logging level (e.g., INFO, DEBUG). | |
| POC_RECORDER_MCP_MAX_STEPS | No | Maximum number of steps allowed per recording run. | 100 |
| POC_RECORDER_MCP_OUTPUT_DIR | No | Directory where output artifacts are written. | |
| POC_RECORDER_MCP_RUN_TIMEOUT | No | Run timeout in seconds. | 180 |
| POC_RECORDER_MCP_SHOW_CURSOR | No | Whether to show the animated virtual cursor (true/false). | true |
| POC_RECORDER_MCP_ALLOWED_HOSTS | No | Comma-separated list or JSON array of allowed hosts. | |
| POC_RECORDER_MCP_SCENARIO_ROOTS | No | Comma-separated list or JSON array of directories to search for reusable scenario files. | |
| POC_RECORDER_MCP_ALLOW_LOCALHOST | No | Whether to allow localhost targets (true/false). | true |
| POC_RECORDER_MCP_MAX_CONCURRENT_RUNS | No | Maximum number of concurrent recording runs. | 2 |
| POC_RECORDER_MCP_AUTO_INSTALL_BROWSER | No | Set to 1 to auto-install the Playwright Chromium browser if missing. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inspect-pageA | Open a target web service URL (including localhost ports) in headless Chromium and return its title, headings, localStorage keys, and interactive DOM selectors (buttons, tabs, inputs, chips, links). Use this before recording to discover accurate selectors. |
| record-pocA | Record an automated video walkthrough of a web PoC or localhost service with an animated virtual cursor, click ripples, optional step HUD captions, and dummy data injection (localStorage, sessionStorage, HTTP route mocks, HTML replacements, or post-load JS). Outputs H.264 |
| list-scenariosB | Discover reusable |
| run-scenarioB | Execute a saved |
| list-recordingsB | List generated |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct step: inspect-page for discovery, record-poc for ad-hoc recording, list-scenarios/run-scenario for saved scenario workflow, and list-recordings for output listing. The only mild overlap is between record-poc and run-scenario, but descriptions make the boundary clear (direct recording vs. executing a saved scenario file).
All five tools follow a consistent kebab-case verb_noun pattern (inspect-page, record-poc, list-scenarios, run-scenario, list-recordings). The convention is uniform and predictable across the set.
Five tools is well-scoped for a recording/automation server, covering discovery, recording, scenario management, and output inspection without redundancy. Each tool earns its place.
The surface covers a full workflow: discover selectors, record ad-hoc, list/run saved scenarios, and list outputs. Minor gaps exist (no tool to create/edit/delete scenario files or prune recordings), but agents can work around these via the filesystem.