Skip to main content
Glama
ceweldy

bitwarden-agent-vault-mcp

by ceweldy

Related Servers

Alternatives to bitwarden-agent-vault-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      MCP server for secure AI agent access to Bitwarden/Vaultwarden vaults with BYOK, exposing tools to list items, reveal secrets via encrypted Sends, get TOTP codes, and save credentials.
      7
      47 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A self-hosted remote MCP server that lets AI agents securely access Bitwarden vaults over HTTPS using OAuth 2.1, without exposing the master password.
      2
      Apache 2.0
    • F
      license
      B
      quality
      D
      maintenance
      MCP server that enables AI models to securely interact with a Bitwarden password manager vault via the rbw CLI.
      11
      1
      -
    • A
      license
      A
      quality
      A
      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
      876 npm
      18
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Secret management MCP server for AI coding agents that prevents secrets from entering the LLM context window by returning metadata only and using side-channel injection. Integrates with Bitwarden and offers hooks for auto-capture and leak prevention.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for agent-native secrets management that stores encrypted secrets with AES-256-GCM, issues short-lived scoped tokens, and injects secrets into requests server-side so agents never handle plaintext credentials.
      39 npm
      MIT

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: retrieving plaintext secrets, listing metadata, running commands with injected secrets, opening the vault, checking status, and storing secrets. No overlapping functionality.

    Naming Consistency4/5

    Most tool names follow a verb_noun pattern (e.g., get_secret, list_projects). The use of 'status' (a noun) and 'run_with_secrets' (verb plus preposition) are minor deviations but still clear.

    Tool Count5/5

    With 7 tools covering key operations (list, get, store, execute, navigate, check), the count is well-scoped for the server's purpose without superfluous tools.

    Completeness4/5

    Core CRUD and lifecycle operations are present, including read, create/update, and execution. Missing a dedicated delete tool, but store_secret can update, so only a minor gap.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues