ucontrol-mcp
Related Servers
Alternatives to ucontrol-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceAn MCP server with HTTP/stdio support, a web admin panel for managing services, capabilities, and user permissions with Bearer token authentication, enabling relay and access control for MCP tools.-
- AlicenseNot gradedqualityDmaintenanceUnified MCP server for ArcGIS Online and Enterprise providing tools for user/group management, item management, geoprocessing, feature layer queries/editing, and server administration.2MIT
- AlicenseNot gradedqualityCmaintenanceA universal MCP server for registering internal, external, and OpenAPI-based APIs as MCP tools. It exposes them to MCP clients via Streamable HTTP and provides admin portal, RBAC/session auth, credential injection, and audit logging.Academic Free v1.1
- FlicenseNot gradedqualityDmaintenanceMCP server providing tools for spatial grid applications including calculations, MongoDB management, asset management, project creation, and experience publishing.-
- AlicenseNot gradedqualityCmaintenanceMCP server for unified SQL database access, supporting multiple databases with schema discovery, caching, and safety controls.10 npmMIT
- FlicenseCqualityDmaintenanceMCP server that enables deployment and management of MCP servers through a simple configuration-based interface.1-
TDQS
Scored across 24 tools
Most tools target distinct resources (protocols, schemas, assets, uMap sub-entities), but some overlap exists between model-related reads (e.g., read_umap_model_details vs. read_umap_models) which could cause misselection. The consistent prefix helps, but the volume of similar read tools creates mild ambiguity.
All tools follow a consistent verb_noun pattern with the prefix 'ucontrol_read_', making the naming highly predictable and uniform. There are no mixed conventions or arbitrary verb choices.
With 24 tools, the server is on the heavy side but justifiable given the multiple sub-APIs it exposes (protocols, schemas, assets, uMap). The count is within a manageable range for the scope, though it approaches the upper limit.
The server is entirely read-only; there are no create, update, or delete tools, which is a significant gap for a 'control' server. The description hints at write protocols but none are implemented, leaving the surface severely incomplete for any management or mutation workflows.