A
licenseNot graded
qualityB
maintenanceEnables AI agents to control and interact with the Windows operating system, including file navigation, application control, UI automation, and QA testing.
MIT
entry-offline-mcp
by l2l2l4
Related Servers
Alternatives to entry-offline-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to see and operate a Windows PC through mouse, keyboard, screenshots, OCR, window control, and shell commands.-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with the Windows operating system, performing tasks such as file navigation, application control, UI interaction, and QA testing.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to inspect and operate Windows applications through structured UI Automation maps, humanized mouse and keyboard input, and on-demand screenshots or OCR via MCP. It supports locating elements by role, name, or query; clicking, typing, scrolling, window management, event watching, and chained multi-step actions without relying on image analysis.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to automate Windows desktop via human-like mouse and keyboard input and UI Automation, with post-action verification for reliable control of programs, UI elements, windows, and files.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to operate Windows computers with parallel, human-like input streams, including held keys, concurrent mouse/keyboard actions, UIA/OCR targeting, and a knowledge base for engineering software.1MIT
TDQS
B3.4/5.0
Scored across 24 tools
Disambiguation4/5
Each tool maps to a distinct resource or action (project, object, scene, data, script, assets, runtime), and descriptions clarify boundaries well. Minor overlaps exist: entry_status vs entry_get_project both summarize the project, entry_screenshot vs entry_run(screenshot=true) duplicate capture, and entry_runtime_state vs entry_run(state=true) overlap for state inspection.
Naming Consistency4/5
All tools share a consistent 'entry_' prefix and snake_case, with readable verb_noun forms for actions (get_project, add_object, set_script, define_function). A few are noun-based aggregates (entry_object_op, entry_scene, entry_data, entry_object_assets), which slightly deviates from the verb pattern but stays readable.
Tool Count3/5
24 tools is at the heavy end, justified by the breadth of the Entry IDE domain (project, scenes, objects, scripts, blocks, assets, runtime testing). It feels borderline heavy, with some redundancy (screenshot/state folded into run plus separate tools) that could be consolidated.
Completeness4/5
Coverage is strong: full project lifecycle (new/open/save/export/import), object and scene CRUD, variables/lists/messages, block and Python scripting, asset library, block reference, run control, input simulation, runtime state, and logging. Only minor gaps like no undo or dedicated script removal (covered by replace) remain.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues