Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-vault

by AIWerk

Related Servers

Alternatives to @aiwerk/mcp-server-vault

No user-submitted related servers found.

    Related Servers

    • 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
    • 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
      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
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server for using Bitwarden Secrets Manager as durable credential storage for agent workflows, enabling secure secret storage, retrieval, and injection into trusted executables.
      7
      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
      C
      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

    TDQS

    A4.1/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool has a largely distinct purpose, and descriptions explicitly cross-reference alternatives (e.g. save_login_item vs save_generated_secret, reveal_secret_via_send vs get_totp_code). The main overlap is list_vault_items vs get_vault_metadata, which both return metadata, though the descriptions clarify listing vs single-item detail.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern (list_vault_items, get_vault_metadata, reveal_secret_via_send, save_generated_secret, save_login_item, get_totp_code). health_check is the only noun-style outlier, but it is a widely conventional name, so consistency is mostly maintained.

    Tool Count5/5

    Seven tools is well-scoped for a vault integration, covering listing, reading, revealing, writing, TOTP, and health. No tool appears redundant or filler.

    Completeness3/5

    Read and create operations are well covered (list, metadata, reveal, save secret, save login, TOTP, health), but the lifecycle is incomplete: there is no update, delete, or revoke operation for items or Sends. Agents cannot modify or clean up existing vault entries, which is a notable gap for a credential store.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues