Bitwarden
Bitwarden is a secure password management solution providing encrypted vaults, cross-platform sync, and enterprise-grade security tools for storing and sharing credentials
Verdict
Common use cases
- Retrieve API keys during campaign setup
- Generate secure passwords for new accounts
- Audit vault for weak or reused credentials
- Rotate secrets after a team member leaves
- Fetch database passwords during incident response
Integration
- Vendor
- Bitwarden
- Category
- other
- Auth
- OAUTH2
- Composio slug
bitwarden
Tools
Setup
Setup guide
- 11. Open your Switchy workspace settings and navigate to the Integrations tab. 2. Click 'Add Integration' and select Bitwarden from the list. 3. You'll redirect to Bitwarden's OAuth consent screen — sign in with an account that has vault access for the items your team needs. 4. Grant the requested scopes: 'vault:read' to retrieve credentials and 'vault:write' to generate new passwords. 5. Bitwarden redirects you back to Switchy with a green confirmation banner. 6. Open any Space and type '@Bitwarden retrieve the staging database password' to test — the MCP should return the credential or prompt you to specify which vault item you mean. 7. If the test fails, check that the Bitwarden account you connected has access to the item you requested and that your organization's vault policies allow API access.
What teammates see: by default, memories from Bitwarden are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Retrieve Staging Credentials
@Bitwarden retrieve the credentials for our staging database. I need the username and password to run a migration script.
Generate Strong Password
@Bitwarden generate a new password for the marketing analytics account. Make it 20 characters with symbols and save it to the shared Marketing folder.
Audit Vault Hygiene
@Bitwarden scan our vault for weak or reused passwords. List any credentials that haven't been rotated in the last 90 days.
Fetch API Key for Integration
@Bitwarden find the API key for our Stripe account. I'm setting up a webhook and need the production key.
Rotate Shared Secret
@Bitwarden rotate the password for our shared Dropbox account. Generate a new one, update the vault, and confirm when it's done.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@bitwarden list all credentials for staging.example.com and show me which ones expire in the next 30 days
Found 4 credentials matching 'staging.example.com'. Two entries expire soon: 'staging-db-admin' (expires Jan 15, 2025) and 'staging-api-key' (expires Jan 22, 2025). The other two credentials ('staging-deploy' and 'staging-monitoring') have no expiration set. All entries are stored in the 'Engineering' collection.
This example shows vault search and filtering. Requires read access to the relevant collections in your Bitwarden organization. The MCP cannot decrypt password values directly — it surfaces metadata (names, URIs, expiration dates) to help you locate the right entry in your vault.
@bitwarden create a new secure note titled 'Q1 2025 API Keys' in the DevOps collection with the contents from the last message
Created secure note 'Q1 2025 API Keys' in the DevOps collection. The note is encrypted and accessible to members with DevOps collection permissions. Item ID: a3f9c2e1-4b8d-4a7e-9c3f-2d1e8b5a6c4d. You can view or edit this note in the Bitwarden web vault or desktop app.
Demonstrates vault write operations. The MCP can create items but cannot read back encrypted field values (passwords, secure note contents) due to Bitwarden's zero-knowledge architecture. Confirm collection permissions before creating items — teammates without access won't see the new entry.
@bitwarden check our vault for any credentials tagged 'production' that haven't been rotated in over 90 days and draft a rotation plan
Scanned 23 production-tagged credentials. Found 7 items last modified more than 90 days ago: 3 database passwords (oldest: 147 days), 2 API keys (oldest: 112 days), 1 SSH key (94 days), and 1 service account (103 days). Recommended rotation order: start with the database credentials due to their age and access scope, then API keys, then the SSH key. The service account can wait until the next sprint if capacity is tight.
Combines vault metadata analysis with AI reasoning to surface security hygiene issues. The MCP provides last-modified timestamps and tags; the AI interprets risk and priority. This workflow does not rotate credentials automatically — it identifies candidates for manual rotation. Rate limits apply if scanning large vaults (500+ items).
Use-case deep-dives
When Bitwarden MCP saves 20 minutes per new hire
A 6-person agency brings on a freelance designer for a 3-week sprint. The PM needs to provision Figma, Notion, and Slack credentials without exposing master passwords or sending plaintext over email. The Bitwarden MCP lets the AI pull shared vault items and generate secure share links in chat, so the PM types "get Sarah set up on the design tools" and the bot handles credential handoff. This works when your team already uses Bitwarden for shared secrets and you onboard people more than twice a month. If you're a solo founder or your secrets live in 1Password, the OAuth setup overhead outweighs the time saved. For teams rotating contractors or managing client access, this MCP turns a 20-minute manual process into a 90-second conversation.
Why support teams skip this MCP for now
A 4-person SaaS support team fields 15 password-reset requests a day for internal staging environments. The idea: let the AI fetch a one-time share link from Bitwarden so agents don't ping engineering. The problem: Bitwarden's OAuth flow requires each agent to authenticate the MCP individually, and the vault structure assumes humans browsing folders, not bots querying by tag or custom field. Without tools captured yet, we can't confirm search or filter capabilities. If your support load is under 5 resets a week, the manual Bitwarden UI is faster. If you're at 20+ resets daily and your vault is already tagged by environment, revisit this MCP in 6 months when tool definitions clarify bulk-lookup patterns. For now, a shared 1Password document beats the integration tax.
When this MCP closes the 2am Slack scramble
A 10-person engineering team gets paged at 2am for a database failover. The on-call engineer needs the root SSH key and the PagerDuty admin token, both buried in a Bitwarden vault the team lead controls. Normally this means waking the lead or hunting Slack threads. With the Bitwarden MCP, the on-call types "get me the prod DB credentials" in the team's AI workspace, the bot authenticates via OAuth, and the secrets appear as secure share links that expire in 15 minutes. This works when your runbooks reference Bitwarden vault names and your on-call rotation includes 3+ people who aren't vault owners. If your team is under 5 engineers or incidents happen less than monthly, the OAuth setup and token refresh cadence add friction you don't need. For teams running 24/7 services with distributed on-call, this MCP cuts mean-time-to-credential from 8 minutes to under 1.
Frequently asked
What does the Bitwarden MCP do in Switchy?
It connects your team's Bitwarden vault to Switchy's AI workspace so agents can retrieve credentials, API keys, and secrets during workflows without exposing them in prompts or logs. The MCP uses OAuth2 to authenticate, meaning you grant read access to specific vault items rather than sharing master passwords. Useful when your AI needs to authenticate against third-party services or pull environment variables stored in Bitwarden.
Do I need admin access to connect Bitwarden via OAuth2?
You need permission to create OAuth2 applications in your Bitwarden organisation settings. Most Bitwarden plans restrict this to admins or owners. If you're on a personal account, you can connect your own vault. The OAuth flow asks for read-only access to vault items, so the MCP can't modify or delete secrets. Check with your IT team if you're unsure about your org's OAuth policies.
Can the Bitwarden MCP create or update vault items?
No. The MCP is read-only by design. It retrieves existing credentials and secrets but can't write new entries, rotate passwords, or modify vault structure. If your workflow needs to generate and store new API keys, you'll need to add them to Bitwarden manually or use Bitwarden's CLI separately. This limitation reduces security risk but means the MCP won't replace your password management workflows.
How does this compare to just pasting secrets into prompts?
Pasting secrets into prompts exposes them in chat history, logs, and potentially in model training data. The Bitwarden MCP fetches credentials at runtime and injects them into tool calls without surfacing them in the conversation. You also avoid the manual copy-paste step every time a workflow needs authentication. The trade-off is setup complexity and OAuth token management, but for teams handling production credentials, it's worth it.
Who on the team should connect the Bitwarden integration?
Whoever owns your team's Bitwarden organisation and understands which vault items the AI should access. This is usually a DevOps lead or security admin. Once connected, all Switchy workspace members can invoke the MCP in their workflows, but they only retrieve secrets the connected Bitwarden account can see. If you're a solo user, connect your personal vault and you're done.