Skip to main content
Glama
K-manankov

platform-mcp

by K-manankov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to platform-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-read-only-argocd

      lukleh
      A
      license
      A
      quality
      C
      maintenance
      A secure MCP server providing read-only access to Argo CD instances using browser session cookies, enabling querying of applications, projects, clusters, and repositories.
      14
      MIT

    • dynamic-shell-server

      codelion
      A
      license
      Not graded
      quality
      F
      maintenance
      A Model Context Protocol (MCP) server that enables secure execution of shell commands with a dynamic approval system, audit logging, and command revocation.
      42
      Apache 2.0

    • @godrix/argocd-mcp

      godrix
      A
      license
      B
      quality
      B
      maintenance
      MCP server for Argo CD that provides multi-environment profiles, SSO or API key authentication, application search with cache, and REST API tools from the bundled OpenAPI catalog.
      26
      4 npm
      MIT

    • argocd-mcp

      severity1
      A
      license
      A
      quality
      D
      maintenance
      An MCP (Model Context Protocol) server that integrates with the ArgoCD API, enabling AI assistants and large language models to manage ArgoCD applications and resources through natural language interactions.
      10
      12
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool is clearly scoped to either Argo CD or Vault, and within each service the login, auth_status, logout, and exec actions are distinct. The system prefix (argocd_ vs vault_) removes any ambiguity between the two sets.

    Naming Consistency5/5

    All tool names follow the consistent pattern {service}_{action} using lowercase snake_case: login, auth_status, logout, exec. The naming is uniform and predictable across both Argo CD and Vault.

    Tool Count5/5

    With 8 tools covering two infrastructure services, the count is well-scoped. Each tool serves a clear and necessary purpose, leaving no redundancy or bloat.

    Completeness5/5

    For a server designed to provide authenticated CLI access to Argo CD and Vault, the tool surface is complete: login, auth status check, logout, and command execution for each system. The exec tools are generic enough to cover the full command surface of both CLIs.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources