Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@rbw-mcp find my GitHub credentials"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Model Context Protocol (MCP) server that enables interaction with the Bitwarden password manager vault via the rbw (Rust Bitwarden) command-line interface. The server allows AI models to securely communicate with a user's Bitwarden vault through defined tool interfaces.
Node.js 22
rbw (Rust Bitwarden CLI) installed and configured.
Related MCP server: bitwarden-agent-vault-mcp
Open up your application configuration, e.g. for Claude Desktop:
{
"mcpServers": {
"rbw": {
"command": "npx",
"args": ["-y", "rbw-mcp"]
}
}
}Requires that this repository be checked out locally. Once that's done:
npm install
npm run buildInstall rbw:
Follow the instructions for your platform on the official rbw repository. For example, on Debian/Ubuntu:
sudo apt-get update
sudo apt-get install rbwConfigure rbw:
Configure rbw to connect to your Bitwarden account.
rbw configUnlock your vault:
Before running the MCP server, you must unlock your vault. This starts the rbw-agent and allows subsequent commands to run without prompting for a password.
rbw unlockThe server will check if the vault is unlocked on startup.
The project includes Jest unit tests.
# Run all tests
npm test
# Run tests in watch mode
npm run test:watch
# Run tests with coverage
npm test -- --coverageUse the MCP Inspector to test the server interactively:
# Start the inspector
npm run inspectThis will:
Start the MCP server
Launch the inspector UI in your browser
Allow you to test all available tools interactively
The server provides the following rbw CLI tools:
Tool | Description | Required Parameters | Notes |
| Lock the vault by clearing cached keys from the agent. | None | Executes |
| Unlock the vault. This will trigger an interactive prompt for your master password if needed. | None | Executes |
| Sync vault data from the Bitwarden server. | None | Executes |
| Check if the vault is unlocked. | None | Executes |
| Lists items from the vault. Can be filtered by a search term. | Optional: | Executes |
| Get a specific field for an item (defaults to password). |
| Executes |
| Get a TOTP code for an item. |
| Executes |
| Generate a secure password or passphrase. By default, generates a strong password with symbols. | Optional: | Executes |
| Delete an item from your vault. |
| Executes |
| Create a new login item in your vault. |
| Executes |
| Edit the password and/or notes for an existing item in your vault. |
| Executes |
Use rbw-agent: It is highly recommended to use rbw with its agent to handle the master password securely.
Validate all inputs: All tool inputs are strictly validated using Zod schemas.
"Vault is locked" error on startup
Run rbw unlock in your terminal before starting the server.
rbw command not found
Ensure that rbw is installed and that its location is in your system's PATH.
Tests failing
Ensure all development dependencies are installed with npm install.
Get a TOTP code for an item from your vault. The id can be a name or UUID. 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.
Inputs: id (required).
Create a new login item in your vault.
Inputs: name (required), uri, notes, password, +1 more.
Delete an item from your vault.
Inputs: id (required).
Edit the password and/or notes for an existing item in your vault.
Inputs: id (required), notes, password.
Generate a secure password or passphrase. By default, generates a strong password with symbols.
Inputs: length, diceware, noSymbols.
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.
Inputs: id (required), field.
Lists items from the vault, always returning name, user, id, and folder. Can be filtered by a search term.
Inputs: search, ignoreCase.
Lock the vault by clearing cached keys from the agent.
Inputs: no named parameters.
Check if the vault is unlocked.
Inputs: no named parameters.
Sync vault data from the Bitwarden server.
Inputs: no named parameters.
Unlock the vault. This will trigger an interactive prompt for your master password if needed.
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
MCP server for Argo RPG Platform — connects AI assistants to campaign data via OAuth2
One MCP server for the services your AI needs: memory, files, Microsoft 365, kanban and more.
MCP server for secureFlows: token-free URL builders and integration-linting tools for AI agents.
