---
title: "Bitwarden MCP server for AI agents - actionlake"
description: "Give Claude 28 Bitwarden actions through one MCP server: members, groups, group members. Your agent never holds the credential. 100,000 calls a month free."
canonical: https://actionlake.com/connectors/bitwarden
updated: 2026-09-24
---

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.

[Connect Bitwarden free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

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/mcp`

the first call

```
do {
  action: "bitwarden.members.list",
  intent: "check which Bitwarden account is connected"
}
# List members · read · 1 upstream call
```

- 28 actions in one signed file
- 12 read look, never change
- 12 write create and update
- 4 wait for a yes destructive, confirmed first

Set up

## Connect Bitwarden in three steps.

1. 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`
2. 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_id` Organization API key client_id (Admin Console > Settings > Organization info > API key; formatted…
   - `client_secret` Organization API key client_secret
   - `api_base` Where your Bitwarden lives: your api base
   - `tenant_host` Where your Bitwarden lives: your tenant host
   ```
   account { op: "connections.requirements", service: "bitwarden" }
   # free: exactly what to paste, and what is found for you
   ```
3. 03
   ### Make the first call. Check before a write.
   Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free.
   ```
   do    { action: "bitwarden.members.list" }
   # list members · read · 1 upstream call
   check { 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_id` `client_secret`

**Setup fields**

`api_base` `tenant_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 2026[OpenAPI spec (GitHub)](https://raw.githubusercontent.com/bitwarden/docs/master/api/specs/public/swagger.json) [bitwarden.com](https://bitwarden.com/help/public-api/) [GitHub](https://raw.githubusercontent.com/bitwarden/server/main/src/Api/AdminConsole/Public/Controllers/MembersController.cs)

**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.

- **12** read look, never change
- **12** write create and update
- **4** destructive wait for a confirmation

1. ### Identity
   28
   12 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.list` List members | All organization members with email, status, type, 2FA state and collection access; continuation-token paged. | read | `identity.user.list` 474 connectors |
| `bitwarden.groups.list` List groups | All groups of the organization; continuation-token paged. | read | `identity.group.list` 262 connectors |
| `bitwarden.members.create` Invite member | Invite a new member to the organization by email with a role and optional collection/group access. | write | `identity.user.create` 262 connectors |
| `bitwarden.groups.create` Create group | Create a group with optional collection access. | write | `identity.group.create` 205 connectors |
| `bitwarden.members.delete` Remove member | Permanently remove a member from the organization (answers an empty 200). | destructive | `identity.user.delete` 253 connectors |
| `bitwarden.group_members.list` List group member ids | Member ids (uuids) that belong to a group; answers a bare array. | read | `identity.group_member.list` 103 connectors |
| `bitwarden.member_groups.list` List member group ids | Group ids (uuids) a member belongs to; answers a bare array. | read | `identity.group_member.list` 103 connectors |
| `bitwarden.members.reinvite` Re-invite member | Re-send the invitation email to an invited member (answers an empty 200). | write | `identity.invitation.send` 15 connectors |
| `bitwarden.policies.list` List policies | Enterprise policies of the organization with type, enabled flag and data; continuation-token paged. | read | `identity.access_policy.list` 13 connectors |
| `bitwarden.policies.update` Update policy | Enable, disable or configure a policy by its type code. | write | `identity.access_policy.update` 15 connectors |
| `bitwarden.events.list` List 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.list` 69 connectors |
| `bitwarden.collections.list` List collections | All collections of the organization with their group assignments; continuation-token paged. | read | `knowledge.password_folder.list` 2 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.

1. Read read
   Who has access in Bitwarden? List every user and their role.
   calls `bitwarden.members.list`
2. Plan destructive
   Retire a group that no longer has members in Bitwarden. Ask me before anything is sent or changed.
   calls `bitwarden.groups.get` `bitwarden.group_members.list` `bitwarden.collections.list` `bitwarden.group_members.replace` `bitwarden.groups.delete`
3. Plan read
   Report who can reach a collection in Bitwarden.
   calls `bitwarden.collections.get` `bitwarden.groups.list` `bitwarden.members.list` `bitwarden.group_members.list`
4. Write write
   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.

1. ### 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.
   **Effect**
   read
   **Steps**
   5 · loops
   **Needs**
   collection id
   **Install**
   `bitwarden-collection-access-report`
2. ### 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.
   **Effect**
   write
   **Steps**
   3 · loops
   **Install**
   `bitwarden-invite-pending-chaser`
3. ### 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.
   **Effect**
   destructive
   **Steps**
   6
   **Needs**
   member id
   **Install**
   `bitwarden-offboard-member`
4. ### 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.
   **Effect**
   destructive
   **Steps**
   6
   **Needs**
   group id
   **Install**
   `bitwarden-retire-empty-group`

install a plan

```
account { op: "plans.install", slug: "bitwarden-collection-access-report" }
# then ask for it by name; a schedule can run it on a timetable
```

Governance 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.

do bitwarden.members.delete confirm_policy: **human**

Remove member?

**intent:** the user asked me to remove member

run suspended · waiting for a named person · key _bitwarden-agent_ cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

```
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: "lead@example.com" },
    { match: "bitwarden.groups.delete", approver: "lead@example.com" },
    { match: "bitwarden.members.revoke", approver: "lead@example.com" }
  ]
}
```

Illustrative. Scoped to Bitwarden only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

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.

- 1 upstream call per action all 28 Bitwarden actions
- 28 actions page each page of a long list is one call
- 11 reads can be cached a cache hit costs nothing
- 100,000 calls a month, free paid plans from US$49 a month for 250,000

[See pricing](https://actionlake.com/pricing)

Action index

## Every Bitwarden action.

28 actions by area: the id your agent calls, what it does, and its effect.

**Identity 28**

- `bitwarden.collections.delete` Delete collection destructive
- `bitwarden.collections.get` Get collection read
- `bitwarden.collections.list` List collections read
- `bitwarden.collections.update` Update collection write
- `bitwarden.events.list` List event logs read
- `bitwarden.group_members.list` List group member ids read
- `bitwarden.group_members.replace` Replace group members write
- `bitwarden.groups.create` Create group write
- `bitwarden.groups.delete` Delete group destructive
- `bitwarden.groups.get` Get group read
- `bitwarden.groups.list` List groups read
- `bitwarden.groups.update` Update group write
- `bitwarden.member_groups.list` List member group ids read
- `bitwarden.member_groups.replace` Replace member groups write
- `bitwarden.members.create` Invite member write
- `bitwarden.members.delete` Remove member destructive
- `bitwarden.members.get` Get member read
- `bitwarden.members.list` List members read
- `bitwarden.members.reinvite` Re-invite member write
- `bitwarden.members.restore` Restore member write
- `bitwarden.members.revoke` Revoke member destructive
- `bitwarden.members.update` Update member write
- `bitwarden.organization_import.create` Import members and groups write
- `bitwarden.organization_subscription.get` Get organization subscription read
- `bitwarden.organization_subscription.update` Update organization subscription write
- `bitwarden.policies.get` Get policy read
- `bitwarden.policies.list` List policies read
- `bitwarden.policies.update` Update policy write

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.

## More connectors like Bitwarden

Shares the most action names with

- [Keycloak Admin REST API 11](https://actionlake.com/connectors/keycloak-admin-rest-api)
- [Opal Security 11](https://actionlake.com/connectors/opal-security)
- [BeyondTrust Password Safe 10](https://actionlake.com/connectors/beyondtrust-password-safe)
- [Cloudflare 8](https://actionlake.com/connectors/cloudflare)
- [Zscaler Internet Access (ZIA) 7](https://actionlake.com/connectors/zscaler-internet-access-zia)
- [Mimecast 6](https://actionlake.com/connectors/mimecast)

Joins with, on shared entities

- [HaloPSA 2](https://actionlake.com/connectors/halopsa)
- [Slack 2](https://actionlake.com/connectors/slack)
- [ServiceNow 2](https://actionlake.com/connectors/servicenow)
- [Fortinet FortiGate 2](https://actionlake.com/connectors/fortinet-fortigate)
- [Genesys Cloud CX 2](https://actionlake.com/connectors/genesys-cloud-cx)
- [Commvault Cloud 2](https://actionlake.com/connectors/commvault-cloud)

Browse

- [All Identity & security connectors](https://actionlake.com/connectors/category/identity-and-security)
- [All connectors](https://actionlake.com/connectors)
- [How actionlake compares](https://actionlake.com/compare)

actionlake is independent. It is not made or endorsed by Bitwarden; the name is the vendor's own. Counts are from the Bitwarden service file, version 1.0.0.

## Give your agent Bitwarden today.

[Connect Bitwarden free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.

---

Source: https://actionlake.com/connectors/bitwarden
More: https://actionlake.com/llms.txt