Skip to main content
Glama
tctibbs

tkinter-mcp-server

by tctibbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to tkinter-mcp-server

No user-submitted related servers found.

    Related Servers

    • qt-mcp

      0xCarbon
      A
      license
      A
      quality
      D
      maintenance
      An MCP server for inspecting, debugging, and interacting with PySide6 desktop applications. It enables AI agents to capture UI snapshots, read widget properties, and perform actions like clicking buttons or typing text.
      22
      2
      Apache 2.0

    • qt-commander

      tiefeiyu
      A
      license
      A
      quality
      B
      maintenance
      MCP server for automating and introspecting native Qt applications (QWidget and QML) without source changes. Enables AI agents to control running Qt apps through UI snapshots, element lookup, and real input simulation.
      25
      2
      MIT

    • PyMCPAutoGUI

      kitfactory
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that bridges AI agents with GUI automation capabilities, allowing them to control mouse, keyboard, windows, and take screenshots to interact with desktop applications.
      23
      MIT

    • OpenEyes

      yangpeng366
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server providing AI-friendly computer-use primitives (capture, detect, click) to let LLM agents drive desktop GUI applications on Windows, macOS, and Linux.
      MIT

    • windows-computer-use-mcp

      betrayzl
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that gives AI agents human-like control over Windows via visual perception and simulated mouse and keyboard input, enabling automation of any application without APIs.
      36 npm
      3
      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.9/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool has a distinct purpose: launching, clicking, dragging, focusing, getting UI layout, reading/writing widget values, etc. Even similar tools like view_application and view_application_thumbnail are differentiated by resolution.

    Naming Consistency4/5

    Tools mostly follow a verb_noun pattern (launch_app, click_widget, set_widget_value) or get_ prefix (get_widget_value, get_window_info). The mix is consistent within subgroups, but not strictly uniform across all tools.

    Tool Count4/5

    16 tools is slightly above the ideal range of 3-15, but the count is justified by the need for various GUI interactions and inspections. It does not feel excessive for the scope.

    Completeness4/5

    Covers core GUI operations: launch, close, click, drag, focus, read layout, read/write values, type text, and screenshots. Missing advanced interactions (e.g., right-click, scroll) but sufficient for fundamental testing.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources