Connectors · Identity & security
Bitwarden MCP server for AI agents.
actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Bitwarden and the rest of your systems. It gives your agent 28 Bitwarden actions (12 reads, 12 writes and 4 that wait for a confirmation) and holds the Bitwarden credential itself, so the agent never does. It paces Bitwarden's limits and records every call.
100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.
claude mcp add --transport http actionlake https://connect.actionlake.com/mcpdo { action: "bitwarden.members.list", intent: "check which Bitwarden account is connected"}# List members · read · 1 upstream call- 28actionsin one signed file
- 12readlook, never change
- 12writecreate and update
- 4wait for a yesdestructive, confirmed first
Set up
Connect Bitwarden in three steps.
- 01
Add actionlake to Claude.
Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
https://connect.actionlake.com/mcp - 02
Connect Bitwarden.
OAuth 2.0, client credentials. Paste the app's client id and secret; actionlake fetches and renews the token, and nobody has to sign in. actionlake stores what you paste write-only, sealed under your tenant's key.
client_idOrganization API key client_id (Admin Console > Settings > Organization info > API key; formatted…client_secretOrganization API key client_secretapi_baseWhere your Bitwarden lives: your api basetenant_hostWhere your Bitwarden lives: your tenant host
account { op: "connections.requirements", service: "bitwarden" } # free: exactly what to paste, and what is found for you - 03
Make the first call. Check before a write.
Ask in plain words; Claude picks the action. Before anything changes,
checkvalidates the call and prices it, for free.do { action: "bitwarden.members.list" }# list members · read · 1 upstream callcheck { action: "bitwarden.members.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent
Bitwarden at a glance
- Sign-in
- OAuth 2.0, client credentials. Paste the app's client id and secret; actionlake fetches and renews the token, and nobody has to sign in.
- You provide
client_idclient_secret- Setup fields
api_basetenant_host- Limits we pace to
- 120 calls a minute, per connection
- API covered
- Bitwarden Public API (organization administration) API public
api.bitwarden.com/public - Built from
- Bitwarden's documentation, read 20 September 2026OpenAPI spec (GitHub)bitwarden.comGitHub
- Service file
- Version 1.0.0, signed (Ed25519)
- Cached reads
- 11 of 12 reads, for up to an hour; a write clears what it affects
- Ready-made plans
- 4 in the store
- Shared entities
- 2, so ask can line Bitwarden up with your other systems
- Data
- Processed and stored in Sydney, Australia. No US region yet
Capabilities
What an AI agent can do in Bitwarden.
28 actions in 1 area. Every one carries its effect, so a key can allow the reads and hold the rest.
- 12readlook, never change
- 12writecreate and update
- 4destructivewait for a confirmation
Identity
2812 read · 12 write · 4 destructive
List members · List groups · Invite member · Create group
Top actions
The Bitwarden API, shaped for agents.
The ids your agent types, what each does, and the one name it shares with other systems. 26 of Bitwarden's 26 action names are shared with at least one other connector, so an agent learns them once.
| Action | What it does | Effect | Same name in |
|---|---|---|---|
bitwarden.members.listList members | All organization members with email, status, type, 2FA state and collection access; continuation-token paged. | read | identity.user.list474 connectors |
bitwarden.groups.listList groups | All groups of the organization; continuation-token paged. | read | identity.group.list262 connectors |
bitwarden.members.createInvite member | Invite a new member to the organization by email with a role and optional collection/group access. | write | identity.user.create262 connectors |
bitwarden.groups.createCreate group | Create a group with optional collection access. | write | identity.group.create205 connectors |
bitwarden.members.deleteRemove member | Permanently remove a member from the organization (answers an empty 200). | destructive | identity.user.delete253 connectors |
bitwarden.group_members.listList group member ids | Member ids (uuids) that belong to a group; answers a bare array. | read | identity.group_member.list103 connectors |
bitwarden.member_groups.listList member group ids | Group ids (uuids) a member belongs to; answers a bare array. | read | identity.group_member.list103 connectors |
bitwarden.members.reinviteRe-invite member | Re-send the invitation email to an invited member (answers an empty 200). | write | identity.invitation.send15 connectors |
bitwarden.policies.listList policies | Enterprise policies of the organization with type, enabled flag and data; continuation-token paged. | read | identity.access_policy.list13 connectors |
bitwarden.policies.updateUpdate policy | Enable, disable or configure a policy by its type code. | write | identity.access_policy.update15 connectors |
bitwarden.events.listList event logs | Organization event log entries (type code, acting user, item/collection/group/policy/member ids, device, IP, date); continuation-token paged. | read | security.audit_log.list69 connectors |
bitwarden.collections.listList collections | All collections of the organization with their group assignments; continuation-token paged. | read | knowledge.password_folder.list2 connectors |
Try it
Prompts to paste into Claude.
Each one names the Bitwarden actions it will call, so you know what it reads and what it changes before you send it.
- Readread
Who has access in Bitwarden? List every user and their role.
calls
bitwarden.members.list - Plandestructive
Retire a group that no longer has members in Bitwarden. Ask me before anything is sent or changed.
calls
bitwarden.groups.getbitwarden.group_members.listbitwarden.collections.listbitwarden.group_members.replacebitwarden.groups.delete - Planread
Report who can reach a collection in Bitwarden.
calls
bitwarden.collections.getbitwarden.groups.listbitwarden.members.listbitwarden.group_members.list - Writewrite
Invite member in Bitwarden. Show me exactly what you will send before you save it.
calls
bitwarden.members.create
The plan store
Ready-made plans for Bitwarden.
4 plans in the store. Install one and your agent runs it by name; the reply says which connections are still missing. A schedule can run a plan on a timetable. There are no triggers or webhooks, by design.
Report who can reach a collection
Use it when An auditor or a security review asks who currently has access to a particular Bitwarden collection.
Re-invite members stuck on pending
Use it when New starters were invited to Bitwarden days ago and several have still not accepted, so the invitations need resending in one pass.
Offboard a departing member
Use it when Someone has left the company and their Bitwarden organization access must be shut off today without destroying their vault data.
A person decides
Revoke Bitwarden access for email, who is in number of data groups and has number of data recent events.
Retire a group that no longer has members
Use it when A Bitwarden group left over from an old team or project needs deleting and you want proof it is empty first.
A person decides
Permanently delete the Bitwarden group name, which granted access to number of collections collections.
account { op: "plans.install", slug: "bitwarden-collection-access-report" }
# then ask for it by name; a schedule can run it on a timetableGovernance for Bitwarden
Destructive actions wait for a yes.
4 Bitwarden actions are destructive. These are all of them:
- Remove member
bitwarden.members.delete - Delete group
bitwarden.groups.delete - Revoke member
bitwarden.members.revoke - Delete collection
bitwarden.collections.delete
A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.
Remove member?
intent: the user asked me to remove member
account { op: "keys.create", name: "bitwarden-agent", allowed_actions: ["bitwarden.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "bitwarden.members.delete", approver: "[email protected]" }, { match: "bitwarden.groups.delete", approver: "[email protected]" }, { match: "bitwarden.members.revoke", approver: "[email protected]" } ]}Cost
What Bitwarden costs on actionlake.
Every Bitwarden action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Bitwarden refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.
- 1upstream call per actionall 28 Bitwarden actions
- 28actions pageeach page of a long list is one call
- 11reads can be cacheda cache hit costs nothing
- 100,000calls a month, freepaid plans from US$49 a month for 250,000
Action index
Every Bitwarden action.
28 actions by area: the id your agent calls, what it does, and its effect.
Identity28
bitwarden.collections.deleteDelete collectiondestructivebitwarden.collections.getGet collectionreadbitwarden.collections.listList collectionsreadbitwarden.collections.updateUpdate collectionwritebitwarden.events.listList event logsreadbitwarden.group_members.listList group member idsreadbitwarden.group_members.replaceReplace group memberswritebitwarden.groups.createCreate groupwritebitwarden.groups.deleteDelete groupdestructivebitwarden.groups.getGet groupreadbitwarden.groups.listList groupsreadbitwarden.groups.updateUpdate groupwritebitwarden.member_groups.listList member group idsreadbitwarden.member_groups.replaceReplace member groupswritebitwarden.members.createInvite memberwritebitwarden.members.deleteRemove memberdestructivebitwarden.members.getGet memberreadbitwarden.members.listList membersreadbitwarden.members.reinviteRe-invite memberwritebitwarden.members.restoreRestore memberwritebitwarden.members.revokeRevoke memberdestructivebitwarden.members.updateUpdate memberwritebitwarden.organization_import.createImport members and groupswritebitwarden.organization_subscription.getGet organization subscriptionreadbitwarden.organization_subscription.updateUpdate organization subscriptionwritebitwarden.policies.getGet policyreadbitwarden.policies.listList policiesreadbitwarden.policies.updateUpdate policywrite
Questions
The Bitwarden MCP server, answered.
Is there a Bitwarden MCP server for Claude?
Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 28 Bitwarden actions, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Bitwarden.
What do I need to connect Bitwarden?
Organization API key client_id (Admin Console > Settings > Organization info > API key; formatted… and Organization API key client_secret. Plus your api base and your tenant host. The free call account { op: "connections.requirements", service: "bitwarden" } lists exactly what to paste.
Can an AI agent delete or change things in Bitwarden?
Only if its key allows it, and only with an explicit confirmation. 4 Bitwarden actions are destructive, including remove member, delete group and revoke member. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.
Will an AI agent use up my Bitwarden API limit?
actionlake paces every call to the limits in the Bitwarden service file: 120 calls a minute per connection. Repeated reads are answered from cache (11 Bitwarden actions can be), which never reaches Bitwarden.
What does a Bitwarden action cost?
One upstream call, the only unit actionlake bills. A list that pages bills one call per page (28 Bitwarden actions page). Cache hits, searches, dry runs and calls Bitwarden refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.
Which Bitwarden API does it cover?
The Bitwarden Public API (organization administration) API public at api.bitwarden.com/public by default, or the base URL set when you connect. It is built from Bitwarden's documentation as read on 20 September 2026. 28 actions in 1 area, each one in the signed service file (version 1.0.0).
Does actionlake keep my Bitwarden data, and where?
actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to an hour, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Bitwarden credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.
Which AI clients can use it?
Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.
Give your agent Bitwarden today.
Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.