qualien-mcp
OfficialRelated Servers
Alternatives to qualien-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA gateway that aggregates multiple MCP servers into a single endpoint, namespacing their tools and forwarding calls, so an agent connects to one MCP to access the entire stack.MIT
- FlicenseNot gradedqualityDmaintenanceA centralized gateway and router that integrates multiple MCP servers into a single endpoint with built-in policy enforcement and secret management. It features a Web GUI for managing tool access, audit logs, and multi-environment configurations across various sub-servers.-
- AlicenseNot gradedqualityAmaintenanceA self-hosted MCP gateway and control plane that aggregates and manages MCP servers and tools, providing unified access, a web console, access control, invocation auditing, and integrated build/deploy workflows.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceA unified MCP gateway that aggregates multiple MCP servers and API plugins behind a single endpoint with authentication, rate limiting, audit logging, REST API bridge, and web dashboard.8MIT
- FlicenseNot gradedqualityNot gradedmaintenanceAggregates multiple MCP servers behind a single, secure endpoint with unified tool/resource discovery, OAuth authentication, and resilient request routing. Enables users to manage and interact with multiple MCP backends through one centralized interface with load balancing and circuit breakers.2-
- AlicenseNot gradedqualityCmaintenanceEnables centralized management, proxying, and aggregation of multiple MCP servers behind unified endpoints, with a web GUI, server groups, tool filtering, and lifecycle controls.9 npmApache 2.0
TDQS
Scored across 39 tools
Most tools target clearly distinct actions (click, hover, drag, navigate, etc.), but a few pairs overlap: read_file is a deprecated duplicate of read_text_file, list_directory essentially duplicates list_directory_with_sizes, and browser_network_requests vs browser_network_request differ only by singular/plural. Descriptions do enough to disambiguate in most cases.
Names follow a consistent snake_case verb_noun pattern (read_text_file, write_file, create_directory, browser_navigate, browser_click) cleanly separated by filesystem__/playwright__ prefixes. Minor deviations like the legacy read_file vs read_text_file and the noun-first browser_console_messages slightly break the pattern.
39 tools is heavy for a single server, though it reflects two bundled domains (filesystem ~14, playwright ~25). Each namespace is reasonable on its own, but combined the surface is on the large side and pushes toward the 'heavy' band.
Playwright coverage is thorough (navigation, interaction, forms, network, dialogs, screenshots, tabs), and filesystem covers read/write/edit/list/search/tree/move/info. However, the filesystem domain has a notable gap: there is no delete/remove tool for files or directories, forcing agents into dead ends for cleanup.