Skip to main content
Glama
privacyplaybook

sops-mcp

by privacyplaybook
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to sops-mcp

No user-submitted related servers found.

    Related Servers

    • simple-secret-storage

      megamen32
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for end-to-end encrypted secret storage and retrieval, enabling LLM agents to fetch secrets by name via one-time URLs while keeping plaintext out of model context and logs.
      1
      -

    • safe-key-mcp

      Yormede
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server enabling AI agents to use secrets (API keys, tokens) via encrypted vault, executing HTTP/shell/SSH actions server-side while never exposing secret values to the AI.
      MIT

    • demipass

      bildow
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for DemiPass secrets management, enabling AI agents to securely store, rotate, and use credentials without exposing them in context windows.
      31 npm
      MIT

    • Agentic Vault

      AliProgrammin
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that lets AI agents call APIs without ever seeing the credentials, using a local encrypted vault and per-secret allowlist policies for HTTP requests and subprocess environment variables.
      1
      AGPL 3.0

    • agent-secrets

      nyx-builds
      A
      license
      Not graded
      quality
      B
      maintenance
      Encrypted secrets management MCP server for AI agents, enabling secure storage, retrieval, rotation, and auditing of API keys and credentials with AES-128 encryption.
      MIT

    • Janee

      rsdouglas
      A
      license
      Not graded
      quality
      C
      maintenance
      Secrets management MCP server that injects credentials into API requests for AI agents, enforcing policies and logging all activity without exposing raw keys.
      31 npm
      30
      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/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: create/add/delete/rename/rotate/update/rekey target different lifecycle operations, and descriptions explicitly define boundaries. The main overlap is the convenience tools sops_create_oidc_secret and sops_create_k8s_secret versus generic sops_create_secrets, though their specialized outputs make the distinction workable.

    Naming Consistency5/5

    Every tool uses the same sops_ prefix, snake_case, and action-oriented naming, generally verb_noun (create_secrets, list_domains, delete_secrets). The few shorter names like sops_rekey are still predictable and consistent with the set.

    Tool Count5/5

    With 12 tools, the server stays within a well-scoped range for a SOPS secrets manager. Each tool corresponds to a meaningful operation, and even the convenience tools earn their place by producing specialized outputs.

    Completeness4/5

    The surface covers the main SOPS lifecycle: create, list, add, delete, rename, rotate, update external values, rekey, metadata, and Kubernetes/OIDC specializations. Minor gaps remain, such as no direct tool for retrieving/decrypting an existing secret value or updating/removing existing metadata.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources