UnClick MCP Server
Related Servers
Alternatives to UnClick MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server that enables AI agents to control Windows by clicking, typing, and navigating with a visible cursor overlay, using a layered approach (native UIA, browser CDP, pixel fallback) for reliable interaction.1-
- AlicenseNot gradedqualityDmaintenanceAn 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.75 npm15AGPL 3.0
- FlicenseBqualityBmaintenanceMCP server that enables AI agents to drive your real, logged-in browser via accessibility snapshots, with hardened credential brokering and local workflow memory.5352 npm-
- AlicenseAqualityCmaintenanceMCP server providing browser automation for AI agents, enabling actions like clicking and typing, structured data extraction, content validation, multi-step task execution, and memory enrichment from web pages.8487 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP 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.67 npm3MIT

agentify-desktopofficial
AlicenseNot gradedqualityDmaintenanceMCP 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.25 npm574Mozilla Public 2.0
TDQS
Scored across 1689 tools
The set contains hundreds of near-duplicate tools across competing providers: crypto prices via CoinGecko, Coinlore, CoinCap, CoinMarketCap, Coinpaprika, plus repeated utility pairs like convert_temperature/temperature_convert, base_convert/number_base_convert, gcd_calculate/gcd_lcm_calc, cat_fact/cat_facts, cat_breeds/cat_api_breeds, json_format/json_prettify, statistics_calc/descriptive_stats, text_readability/readability_score. Categories like weather, quotes, jokes, IP geolocation, and exchange rates each have 3-6 overlapping tools an agent cannot reliably choose between. At 1689 tools, an agent has no realistic path to picking the right one.
Many tools follow a provider_prefix_verb convention (tmdb_search_movies, jira_get_issue), but the naming is broadly inconsistent: verb-first without provider (list_calendly_events, get_steam_app_details, create_monday_item), noun-only (is_even, do_account, heartbeat_protocol), and opaque catch-all multiplexers with action parameters (slack_action, notion_action, mastodon_action). Fetch verb varies between get/read/fetch/lookup for identical operations.
1689 tools is an extreme mismatch for any coherent server purpose; even a large aggregator should namespace into separate servers. The count reflects unbounded accretion of integrations rather than a scoped surface, and a large fraction of the tools duplicate each other's function.
Coverage is extraordinarily broad—read paths exist for most public APIs and many SaaS platforms—so few obvious holes remain at the resource-coverage level. However, write/mutation coverage is thin and uneven (many integrations are list/get only: Stripe invoices, Xero, Klaviyo, Brickset), and there are dead ends like the retired fishwatch_species tools and legacy UXPass/FlowPass runners, so lifecycle completeness is inconsistent per domain.