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.28 npmApache 2.0
TDQS
Scored across 38 tools
The tools are mostly distinct as they are grouped by 'playwright__' and 'filesystem__' prefixes and have clear action-target descriptions, though a few like 'read_file' and 'read_text_file' could be confused, especially with the deprecation note.
The naming convention is largely consistent with a pattern of 'module__verb_noun' (e.g., playwright__browser_click, filesystem__read_text_file). Minor inconsistency arises with some 'playwright__browser_' tools that use somewhat different verb phrasing (e.g., 'run_code_unsafe' vs 'evaluate'), and the presence of a deprecated 'read_file' alongside the preferred 'read_text_file' is confusing.
With 38 tools, the set is on the high side. While it covers browser automation and file system operations fairly thoroughly, the sheer number could be overwhelming and suggests potential for consolidation or trimming of overlapping or rarely useful tools.
The file system tools provide a comprehensive set for read, write, edit, search, and directory management. The browser tools cover navigation, interaction, and inspection well. Minor gaps exist, such as lacking a dedicated tool for clearing browser data or handling multiple dialogs, but the core workflows are well supported.