open-worship-app-mcp
OfficialRelated Servers
Alternatives to open-worship-app-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceLets AI agents lease a single Windows window or a whole screen, see its controls, click, type and hotkey inside it (in the background, so the user keeps their own mouse and keyboard), and record what they did as a step-by-step tutorial. Every action passes through policy checks — one driver at a time, hard denies on elevated/password/secure-desktop targets, approvals for risky clicks, and logged refusals.MIT
- AlicenseNot gradedqualityBmaintenanceGives MCP-compatible AI agents a local, observable control plane for Edge, Chrome/Chromium, and Firefox, combining DOM/accessibility, screenshots, Windows UI Automation, and real mouse/keyboard input with verification, approvals, and audit logging.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to inspect and drive native Windows desktop applications (WinForms, WPF, WinUI 3, and WebView2 hybrids) through Microsoft UI Automation by capturing interactive control snapshots, then clicking, filling, and asserting on elements via ephemeral refs or semantic screen-map targets. Mutating actions are dry-run by default and gated behind explicit arming, allow-lists, and a kill switch for lawful, assisted QA testing.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to observe and control the user's live desktop by listing apps, reading accessibility trees, and performing clicks, typing, scrolling, dragging, and other input actions with per-action approvals and local audit archives.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to inspect and control allowlisted Windows applications using screenshots, mouse actions, Unicode keyboard input, UI Automation, and an Esc/F12 emergency stop.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to operate Windows desktops through native UIA control, OCR text targeting, screenshots, and 54 tools for window, process, input, clipboard, file, registry, and document tasks with pause, observe-only, and privacy safeguards.MIT
TDQS
Scored across 76 tools
Two parallel UI-driving surfaces exist: the generic Playwright-style tools (click, fill, hover, press_key, drag, take_snapshot) and the app-specific ones (owa_click, owa_type, owa_press_key, owa_drag, owa_list_ui, owa_find_ui). An agent must decide which family to use for the same action, and nothing in the names settles it. There is also heavy overlap within the domain: owa_lyric_file vs owa_lyric_edit, owa_slide_file vs owa_slide_edit, owa_presenting_flow vs owa_presenting_flow_edit, owa_foreground vs owa_foreground_edit, plus owa_bible_item/owa_bible_note/owa_bible_xml/owa_lookup_record.
Names are uniformly snake_case and most follow verb_noun (owa_present_bible, owa_create... , list_console_messages, navigate_page). But the owa_ prefix is applied inconsistently relative to the unprefixed browser tools, and many domain tools are noun-only or compound (owa_app_state, owa_menu, owa_help_page, owa_lyric_file, owa_bible_xml). Readable, but the convention breaks down across the set.
76 tools is far past what this domain justifies, and a large share are duplicates of each other (generic page automation alongside app-specific equivalents, plus _file/_edit pairs for songs, slides, notes, flows, and foregrounds). The surface reads like two servers merged into one rather than a well-scoped set.
Coverage is genuinely broad: CRUD for songs, slides, notes, Bibles, saved passages, media, run sheets, screens, plus undo, help/knowledge search, language, screenshots, and guided walkthroughs. Remaining gaps are minor and mostly workaround-able rather than dead ends.