Skip to main content
Glama
gorbabor

mc-iclone8-ui-mcp

by gorbabor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mc-iclone8-ui-mcp

No user-submitted related servers found.

    Related Servers

    • Computer Control MCP

      AB498
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides computer control capabilities including mouse movements, keyboard actions, screenshot capture with OCR, and window management through a unified API.
      258 PyPI
      167
      MIT

    • vred-mcp

      krngrover6
      A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that enables MCP-compatible AI clients to inspect and control the currently open scene in a running Autodesk VRED Professional 2027 instance via a secure bridge, supporting read-only inspection and gated mutations like selection, visibility, transforms, and screenshots.
      MIT

    • pc-control-agent

      anbu-20012005
      F
      license
      Not graded
      quality
      C
      maintenance
      This MCP server enables an AI agent to control a Windows PC through human-like interactions such as screen capture, OCR, mouse, keyboard, and navigation, without using shortcut APIs.
      -

    • umbriel

      ObscuritySRL
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for driving any Windows app through five layers including OCR, UI Automation, and direct OS operations. Enables AI agents to control Windows desktop and OS cursor-free, even on background/locked windows.
      63 npm
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct aspect: screen capture, visible state reading, workflow control, application inspection, and accessibility tree inspection. No ambiguity exists between their purposes.

    Naming Consistency5/5

    All tool names follow a consistent pattern: <scope>.<action> with snake_case action names (e.g., ui.capture_screen, scene.read_visible_state).

    Tool Count5/5

    With 5 tools covering capture, state, workflow, and inspection, the count is well-scoped for a UI monitoring server.

    Completeness4/5

    Covers capture, state reading, and two inspection methods, plus workflow stop. Missing tools for starting workflows or retrieving detailed element properties, but serves its monitoring purpose adequately.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources