Bitwarden runs on your own machine — the client starts it, so there is no endpoint to ping. 480 installs a week from npm. Last commit 3 Nov 2026.
Give your assistant its own Bitwarden vault for logins, passwords, 2FA codes and passkeys.
Nothing serious here today
Today is the operative word: we check Bitwarden every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add bitwarden -e 'BITWARDEN_CLIENT_ID_FILE=<BITWARDEN_CLIENT_ID_FILE>' -e 'BITWARDEN_CLIENT_SECRET_FILE=<BITWARDEN_CLIENT_SECRET_FILE>' -e 'BITWARDEN_MASTER_PASSWORD_FILE=<BITWARDEN_MASTER_PASSWORD_FILE>' -- npx -y @foreverworks/mcp-bitwarden{
"mcpServers": {
"bitwarden": {
"command": "npx",
"args": [
"-y",
"@foreverworks/mcp-bitwarden"
],
"env": {
"BITWARDEN_CLIENT_ID_FILE": "<BITWARDEN_CLIENT_ID_FILE>",
"BITWARDEN_CLIENT_SECRET_FILE": "<BITWARDEN_CLIENT_SECRET_FILE>",
"BITWARDEN_MASTER_PASSWORD_FILE": "<BITWARDEN_MASTER_PASSWORD_FILE>"
}
}
}
}[mcp_servers.bitwarden]
command = "npx"
args = ["-y", "@foreverworks/mcp-bitwarden"]
env = { BITWARDEN_CLIENT_ID_FILE = "<BITWARDEN_CLIENT_ID_FILE>", BITWARDEN_CLIENT_SECRET_FILE = "<BITWARDEN_CLIENT_SECRET_FILE>", BITWARDEN_MASTER_PASSWORD_FILE = "<BITWARDEN_MASTER_PASSWORD_FILE>" }{
"mcpServers": {
"bitwarden": {
"command": "npx",
"args": [
"-y",
"@foreverworks/mcp-bitwarden"
],
"env": {
"BITWARDEN_CLIENT_ID_FILE": "<BITWARDEN_CLIENT_ID_FILE>",
"BITWARDEN_CLIENT_SECRET_FILE": "<BITWARDEN_CLIENT_SECRET_FILE>",
"BITWARDEN_MASTER_PASSWORD_FILE": "<BITWARDEN_MASTER_PASSWORD_FILE>"
}
}
}
}{
"servers": {
"bitwarden": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@foreverworks/mcp-bitwarden"
],
"env": {
"BITWARDEN_CLIENT_ID_FILE": "<BITWARDEN_CLIENT_ID_FILE>",
"BITWARDEN_CLIENT_SECRET_FILE": "<BITWARDEN_CLIENT_SECRET_FILE>",
"BITWARDEN_MASTER_PASSWORD_FILE": "<BITWARDEN_MASTER_PASSWORD_FILE>"
}
}
}
}Put your own values in place of
<BITWARDEN_CLIENT_ID_FILE> (Path of a file holding the account's API key client id), <BITWARDEN_CLIENT_SECRET_FILE> (Path of a file holding the API key's client secret), <BITWARDEN_MASTER_PASSWORD_FILE> (Path of a file holding the master password that unlocks the vault).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
BITWARDEN_SERVER (A self-hosted or EU server, e.g. https://vault.bitwarden.eu. Leave empty for bitwarden.com).
Alternatives to Bitwarden
same job, measured the same wayMCP server for Enpass vaults: entries, passwords and TOTP/2FA codes, keychain-backed.
Give your AI assistant its own email inbox: send, read and catch sign-in codes. Texting coming soon.
Bitwarden/Vaultwarden for agents: list tagged items, TOTP codes, one-time Sends, save new secrets.
AI code review for your AI assistant — review local changes, branch diffs, and patch files.
Create short links, QR codes, UTM templates, vCards, and landing pages from your AI assistant.
Use your OTPilot accounts (passwords, 2FA codes) to sign in and run commands, without seeing them.
Encrypted local vault for API keys. Your AI fetches keys on demand and scans code for leaks.
Code review on your own machine, for you and your coding agent. Nothing leaves your computer.
Bitwarden — questions
Answers built from our own checks of this server.