Skip to main content
Glama
AgentVault MCP Server

AgentVault MCP Server

Related Servers

Alternatives to AgentVault MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding tools to securely manage secrets via MCP tools for vault operations, diagnostics, and cloud sync, ensuring real keys never enter the LLM context.
      20
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to request and retrieve credentials from a Bitwarden-compatible vault through MCP tools, with human approvals, short-lived grants, audit logging, and optional OAuth 2.1 authentication. It also supports creating secrets and injecting them into child processes without exposing them to the model.
      AGPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to securely manage API keys and secrets via the MCP protocol, with encrypted storage at rest and a simple CLI and Python SDK.
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI memory persistence and secure credential management via vault tools for MCP-compatible clients like Claude Desktop, Cursor, and VS Code.
      12
      9 npm
      MIT
    • 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
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for Vaultwarden/Bitwarden vault management. Enables AI agents to securely create, search, read, and update vault items via the official Bitwarden CLI, with safe-by-default redaction and support for both stdio and SSE transports.
      53
      1,933 npm
      26
      MIT

    TDQS

    B3.2/5.0

    Scored across 7 tools

    Disambiguation4/5

    While av_get_secret and av_resolve both retrieve secret data, av_get_secret returns the full field map while av_resolve targets a specific field via reference. av_put_secret and av_rotate_secret are similarly distinct (create/update vs. replace). The purposes are mostly clear, though the boundary between get/resolve and put/rotate could momentarily confuse.

    Naming Consistency4/5

    The av_ prefix is consistent, and most tools follow av_<verb>_<noun> (create_vault, put_secret, get_secret, list_secrets, issue_token, rotate_secret). The verb style is uniform, but 'av_resolve' lacks an explicit object, a minor deviation.

    Tool Count5/5

    With 7 tools, the set is well-scoped for a vault management server, fitting the typical 3-15 range. Each tool addresses a distinct operation without redundancy or bloat.

    Completeness4/5

    The server covers the core lifecycle of vaults and secrets: create, read, update, list, rotate, and token issuance. However, there is no delete operation for vaults or secrets, which could be considered a gap for complete lifecycle management, though it may be intentional for security.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data