UnClick MCP Server
Related Servers
Alternatives to UnClick MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceAn open-source MCP server for macOS and Windows that provides native desktop control via Accessibility APIs, OCR, and Chrome CDP. It enables AI agents to interact with applications, manage browser sessions, and automate workflows with high-speed native UI actions.89 npm15AGPL 3.0

agentify-desktopofficial
AlicenseNot gradedqualityBmaintenanceMCP server that enables AI tools to control local browser sessions for ChatGPT, Claude, and other AI services, supporting querying, navigation, file uploads, and artifact management.35 npm564Mozilla Public 2.0- FlicenseNot gradedqualityDmaintenanceMCP server that enables AI agents to automate browser testing via Chromium, providing tools for navigation, interaction, and inspection.-
- AlicenseAqualityBmaintenanceMCP server that gives AI coding assistants direct access to the browser — navigate, click, fill forms, run JavaScript, take screenshots, and read page content.1110 npm1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for macOS that enables AI agents to control the desktop GUI through keyboard input, mouse actions, and screen captures. It provides stable low-level primitives for UI automation and agent-driven desktop workflows.MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP Server that enables AI assistants to interact with your local browsers.2,256 npm54MIT
TDQS
Scored across 813 tools
The server aggregates an enormous and unrelated collection of tools from dozens of distinct domains, many with overlapping purposes (e.g., crypto_price vs cmc_quotes vs stock_quote, weather_forecast vs tomorrow_forecast vs willyweather_forecast, multiple search/search variants). Multiple generic 'action' tools (notion_action, github_action, etc.) abstract many sub-actions, creating ambiguity about which tool to call. Almost no tool has a unique, non-overlapping role across the set.
Naming uses no consistent pattern: some tools use verb_noun (sendle_get_quote, list_calendly_event_types), some use noun_verb (mc_quotes, weather_forecast), many use bare domain prefixes (amber_sites, esports_matches), and several are generic 'action' tools (slack_action, github_action). Conventions are wildly mixed with no discernible consistent style.
With 813 tools, this is a massive aggregate of almost every possible MCP integration, far beyond any single-purpose server. The count is extreme and unwieldy, making it nearly impossible for an agent to efficiently select the right tool. Many tools cover overlapping functionality across different providers.
The server attempts to cover an impossibly broad domain (global APIs, productivity, finance, gaming, media, etc.), but individual areas are often incomplete: many CRUD operations are missing (e.g., no update for many resources), several providers only expose partial endpoints, and no coherent lifecycle is covered for any single domain. The enormous breadth makes meaningful completeness assessment impossible, but obvious gaps exist (e.g., serious lack of write operations in many integrations).