Skip to main content
Glama
dceluis

rbw-mcp

by dceluis

Related Servers

Alternatives to rbw-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      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
      50 npm
      MIT
    • 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
      548 npm
      17
      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.
      1
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that gives Claude scoped, indirect access to Vaultwarden credentials by listing non-secret metadata and performing logins without exposing plaintext passwords. It brokers actions rather than values, keeping secrets out of the LLM context.
      -
    • A
      license
      A
      quality
      B
      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

    TDQS

    B3.2/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools are clearly distinct (status vs unlock vs lock vs sync; create/edit/delete vs list/get). The only minor ambiguity is between 'list' and 'get' — both retrieve vault items, though one returns fields for a specific item and the other enumerates items. The distinction is reasonably clear from descriptions.

    Naming Consistency4/5

    All tools use short, single-word imperative names (status, create, edit, generate, lock, unlock, sync, list, get, code, delete). The style is consistent, though the names are generic single verbs rather than a verb_noun pattern, which slightly reduces predictability compared to the ideal convention.

    Tool Count4/5

    With 11 tools for a Bitwarden password manager vault, the surface is appropriately scoped. Each tool maps to a distinct vault operation (locks, item CRUD, sync, TOTP, generation), and none feel redundant. The count is slightly on the higher side but still well within reason.

    Completeness4/5

    The surface covers vault lifecycle (unlock/lock/status/sync), item CRUD (list/get/create/edit/delete), TOTP retrieval, and password generation. Minor gaps include no ability to manage folders, move items between folders, or handle multiple vaults/collections, but the core password-management workflows are covered with no dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues