A
licenseNot graded
qualityB
maintenanceEnables AI agents to automate desktop operating systems and applications through UI automation, screenshots, and input simulation.
1
MIT
EchoPath MCP Server
by JackZhao1998
Related Servers
Alternatives to EchoPath MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables an AI agent to operate Windows applications through vision-driven UI Automation and record polished demo videos with pre-click camera zoom, narration, and cinematic effects.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to control Windows GUI applications like a human using screen capture, OCR, mouse and keyboard input, and window management, with safety levels and memory.-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to see and control your desktop with tools for screenshots, clicks, typing, and more, all locally on macOS and Windows.138 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to drive any Windows desktop app through window-relative, token-efficient tools, with optional DeepSeek-powered vision.Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to see and operate a Windows PC through mouse, keyboard, screenshots, OCR, window control, and shell commands.-
TDQS
B3/5.0
Scored across 17 tools
Disambiguation2/5
Several tool pairs have overlapping boundaries: start_task vs run_task both launch work, and resume vs resume_task both continue an awaiting_native task, with only subtle wording to distinguish them. The task/run/session/procedure/memory taxonomy is fuzzy (list_runs vs list_sessions, list_procedures vs list_memories), so an agent could easily misselect.
Naming Consistency4/5
Nearly every tool follows a consistent snake_case echopath_verb_noun pattern (list_runs, control_run, get_procedure, create_session, clear_history). A few deviate with a bare verb or compound (resume, consolidate, smoke_check), but the convention is predictable overall.
Tool Count3/5
17 tools is on the heavy side, and the overlap between start_task/run_task and resume/resume_task suggests some could be merged rather than each earning its place. The multi-faceted domain (tasks, runs, sessions, procedures, memories) justifies breadth, but it is borderline bloated.
Completeness4/5
Coverage is broad: task lifecycle (start, resume, get, control), sessions (create, get, list), procedures (list, get), memories (list, consolidate), plus status and health checks. Minor gaps exist (no get_run by id, no delete/close for sessions or tasks), but core workflows are workable.
Maintenance
ActivityMaintained
ResponsivenessNo issues