rbw-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lockA | Lock the vault by clearing cached keys from the agent. |
| unlockB | Unlock the vault. This will trigger an interactive prompt for your master password if needed. |
| syncC | Sync vault data from the Bitwarden server. |
| statusC | Check if the vault is unlocked. |
| listA | Lists items from the vault, always returning name, user, id, and folder. Can be filtered by a search term. |
| getA | Get a specific field for an item (defaults to password). It is highly recommended to use the 'list' tool first to find the exact item ID. The response includes a top-level 'metadata' object with a 'secret: true' flag, which a gateway can intercept for sanitization or to provide secure handle-based access. |
| codeA | Get a TOTP code for an item from your vault. The |
| generateB | Generate a secure password or passphrase. By default, generates a strong password with symbols. |
| createC | Create a new login item in your vault. |
| editC | Edit the password and/or notes for an existing item in your vault. |
| deleteC | Delete an item from your vault. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
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.
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.
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.
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.