Back to MCP Servers
🧩

Bitwarden Public API and Secrets Manager (unofficial) MCP Server

API key required

Unofficial MCP server for the Bitwarden Public API and Secrets Manager, self-hosted or cloud.

To add Bitwarden Public API and Secrets Manager (unofficial) to Claude, run the install command below or copy the ready-made config for Claude Code, Claude Desktop, Cursor and VS Code further down. Restart your client after adding it and its tools show up in your next conversation. It needs 16 environment variables, listed below.

APICloudDevTools

Install

npx -y the-real-bitwarden-mcp@0.3.1

Environment variables

BITWARDEN_SELFHOST_API_BASESet in your MCP config
BITWARDEN_SELFHOST_IDENTITY_URLSet in your MCP config
BITWARDEN_SELFHOST_CLIENT_IDSet in your MCP config
BITWARDEN_SELFHOST_CLIENT_SECRETSet in your MCP config
BITWARDEN_CLOUD_API_BASESet in your MCP config
BITWARDEN_CLOUD_IDENTITY_URLSet in your MCP config
BITWARDEN_CLOUD_CLIENT_IDSet in your MCP config
BITWARDEN_CLOUD_CLIENT_SECRETSet in your MCP config
BWS_ACCESS_TOKENSet in your MCP config
BWS_ORG_IDSet in your MCP config
BWS_API_BASESet in your MCP config
BWS_IDENTITY_URLSet in your MCP config
BITWARDEN_CONFIRM_WRITESSet in your MCP config
BITWARDEN_READ_ONLYSet in your MCP config
LOG_LEVELSet in your MCP config
BW_MCP_MAX_RESPONSE_BYTESSet in your MCP config

Install with your client

Terminal
claude mcp add bitwarden-public-api-and-secrets-manager-unofficial --env BITWARDEN_SELFHOST_API_BASE=<YOUR_BITWARDEN_SELFHOST_API_BASE> --env BITWARDEN_SELFHOST_IDENTITY_URL=<YOUR_BITWARDEN_SELFHOST_IDENTITY_URL> --env BITWARDEN_SELFHOST_CLIENT_ID=<YOUR_BITWARDEN_SELFHOST_CLIENT_ID> --env BITWARDEN_SELFHOST_CLIENT_SECRET=<YOUR_BITWARDEN_SELFHOST_CLIENT_SECRET> --env BITWARDEN_CLOUD_API_BASE=<YOUR_BITWARDEN_CLOUD_API_BASE> --env BITWARDEN_CLOUD_IDENTITY_URL=<YOUR_BITWARDEN_CLOUD_IDENTITY_URL> --env BITWARDEN_CLOUD_CLIENT_ID=<YOUR_BITWARDEN_CLOUD_CLIENT_ID> --env BITWARDEN_CLOUD_CLIENT_SECRET=<YOUR_BITWARDEN_CLOUD_CLIENT_SECRET> --env BWS_ACCESS_TOKEN=<YOUR_BWS_ACCESS_TOKEN> --env BWS_ORG_ID=<YOUR_BWS_ORG_ID> --env BWS_API_BASE=<YOUR_BWS_API_BASE> --env BWS_IDENTITY_URL=<YOUR_BWS_IDENTITY_URL> --env BITWARDEN_CONFIRM_WRITES=<YOUR_BITWARDEN_CONFIRM_WRITES> --env BITWARDEN_READ_ONLY=<YOUR_BITWARDEN_READ_ONLY> --env LOG_LEVEL=<YOUR_LOG_LEVEL> --env BW_MCP_MAX_RESPONSE_BYTES=<YOUR_BW_MCP_MAX_RESPONSE_BYTES> -- npx -y the-real-bitwarden-mcp@0.3.1

Run this in a terminal to add the server to Claude Code.

What this does

Bitwarden Public API and Secrets Manager (unofficial) exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

BITWARDEN_SELFHOST_API_BASE
BITWARDEN_SELFHOST_IDENTITY_URL
BITWARDEN_SELFHOST_CLIENT_ID
BITWARDEN_SELFHOST_CLIENT_SECRET
BITWARDEN_CLOUD_API_BASE
BITWARDEN_CLOUD_IDENTITY_URL
BITWARDEN_CLOUD_CLIENT_ID
BITWARDEN_CLOUD_CLIENT_SECRET
BWS_ACCESS_TOKEN
BWS_ORG_ID
BWS_API_BASE
BWS_IDENTITY_URL
BITWARDEN_CONFIRM_WRITES
BITWARDEN_READ_ONLY
LOG_LEVEL
BW_MCP_MAX_RESPONSE_BYTES

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

Frequently asked questions

How do I install Bitwarden Public API and Secrets Manager (unofficial)?

Run the Claude Code command in the install section to add Bitwarden Public API and Secrets Manager (unofficial) to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with Bitwarden Public API and Secrets Manager (unofficial)?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to Bitwarden Public API and Secrets Manager (unofficial) as well.

Does Bitwarden Public API and Secrets Manager (unofficial) need an API key?

Yes. Before it can run, set these environment variables: BITWARDEN_SELFHOST_API_BASE, BITWARDEN_SELFHOST_IDENTITY_URL, BITWARDEN_SELFHOST_CLIENT_ID, BITWARDEN_SELFHOST_CLIENT_SECRET, BITWARDEN_CLOUD_API_BASE, BITWARDEN_CLOUD_IDENTITY_URL, BITWARDEN_CLOUD_CLIENT_ID, BITWARDEN_CLOUD_CLIENT_SECRET, BWS_ACCESS_TOKEN, BWS_ORG_ID, BWS_API_BASE, BWS_IDENTITY_URL, BITWARDEN_CONFIRM_WRITES, BITWARDEN_READ_ONLY, LOG_LEVEL, BW_MCP_MAX_RESPONSE_BYTES. They go in the env block of your MCP config.

Imported from the Official MCP Registry. The details above come from the registry entry; the maker can claim this listing to correct them, add docs, and see its traffic.

Is this your MCP server?

Claim this listing to see its traffic, fix details yourself, and skip the review queue on future updates.

Listed on clauderules.net

Add this badge to your README

Show visitors this server is listed in the ClaudeRules directory. The badge links straight to this listing.

Markdown
[![Listed on clauderules.net](https://clauderules.net/api/badge/io-github-mguttmann-the-real-bitwarden-mcp)](https://clauderules.net/mcp/io-github-mguttmann-the-real-bitwarden-mcp)
HTML
<a href="https://clauderules.net/mcp/io-github-mguttmann-the-real-bitwarden-mcp" target="_blank" rel="noopener noreferrer"><img src="https://clauderules.net/api/badge/io-github-mguttmann-the-real-bitwarden-mcp" alt="Listed on clauderules.net" /></a>