Karakoram
Related Servers
Alternatives to Karakoram
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server for managing a self-hosted Coolify instance. Provides full REST CRUD, deploy/watch capabilities, and an optional host-ops tier for live log streaming, SSH, Docker, and database access.2212 npmMIT
- AlicenseNot gradedqualityCmaintenanceSelf-hosted MCP proxy and aggregation platform. Register multiple upstream MCP servers and expose them through a single unified endpoint with namespace routing, multi-transport support (HTTP/SSE, stdio, OpenAPI→MCP), per-tool overrides, and a web admin UI.18MIT
- AlicenseNot gradedqualityCmaintenanceMCP server and CLI for host and container operations, enabling Docker and Compose control, SSH, host inspection, logs, ZFS, and safe file transfer. It exposes flux and scout MCP tools with parity from the original TypeScript server.2AGPL 3.0
- AlicenseAqualityDmaintenanceA self-hostable PostgreSQL MCP server for exploring database schemas and running guarded read/write queries with selectable access modes (readonly, readwrite, admin), plus a dry-run confirm workflow for safety.141MIT
- AlicenseAqualityAmaintenanceOne MCP server to manage self-hosted Coolify instances: verify connectivity, discover servers, deploy applications, tail logs, diagnose incidents, and run emergency ops from any MCP client.1938 npmMIT
- FlicenseAqualityDmaintenanceRead-only MCP server that exposes Kubernetes platform state (tenants, pods, SLOs, ArgoCD applications, chaos schedules, and catalog services) to AI agents, enabling natural language queries about cluster health and configuration.6-
TDQS
Scored across 93 tools
Many get/list pairs are resource-specific and descriptions are detailed, but several tools overlap: cluster_get vs cluster_status_get vs cluster_diagnose, account_get vs current_user_get/system_users_list, operations_list vs cluster_operations_list, and permissions_get vs permission_check/rbac_policy_get. These boundaries will cause some misselection.
Nearly all names use snake_case noun_verb patterns such as resource_get, resources_list, permission_check, and engine-prefixed variants. Singular get vs plural list is applied consistently, and the few outliers like wait remain readable within the same convention.
93 tools is far beyond the well-scoped 3-15 range and exceeds the 50+ threshold for extreme count mismatch. The surface is fragmented into many per-resource get/list pairs across multiple engines, making the server unwieldy.
The surface is overwhelmingly read-only: it exposes list/get for clusters, backups, restores, users, roles, tokens, policies, and settings but lacks create/update/delete/start/cancel/revoke operations. For an infrastructure control plane, these are significant lifecycle gaps that will block many agent workflows.