# Bitwarden MCP connector

Connect Bitwarden to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent can list, invite, and update Bitwarden organization members, groups, collections, and policies as the signed-in person, with every call logged.

Source: https://elaichi.ai/connectors/bitwarden/

## Facts

| | |
| --- | --- |
| Application | Bitwarden |
| Category | Password Manager |
| AI tools | 28 |
| Authentication | App credentials |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Bitwarden is connected

- Who is in the Engineering group in Bitwarden?
- Resend the invite to every member who has not accepted yet.
- Which policies are turned on for our organization right now?

## Connect Bitwarden in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Bitwarden.
2. Optionally set Share with, then press Connect.
3. Paste your Bitwarden app credentials. Bitwarden authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Bitwarden tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Bitwarden MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Bitwarden MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Bitwarden MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Bitwarden MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Bitwarden MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Bitwarden to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Bitwarden tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Bitwarden through Elaichi

### Onboard a new hire into Bitwarden

IT. Invite the person as a member, add them to the right groups, and confirm which collections those groups reach, all from one request after the start date is confirmed.

### Resend a Bitwarden invite that expired

Helpdesk. Find the member who never accepted and send the invite again without opening the admin console or asking the person to raise a ticket.

### Review who can reach a collection

Security. Ask which groups are attached to a collection and which members sit in those groups before an access review meeting, then tidy the groups on the spot.

### Check and tighten organization policies

Security. Read the current Bitwarden policies, such as the two-step login requirement, and update one when the company standard changes.

### Offboard a leaver from the organization

People operations. Pull the person out of every group and remove them as a Bitwarden member on their last day, so nothing lingers after the laptop is handed back.

### Pull the event history for a review

Compliance. List recent organization events, such as invites, group changes, and policy updates, and summarize them for the quarterly access review.

## Elaichi vs Zapier MCP vs Composio for Bitwarden

All three can connect Bitwarden to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Bitwarden tools | Allow or restrict single Bitwarden tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Bitwarden call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Bitwarden to Claude?

Connect Bitwarden in Elaichi first: Bitwarden asks for your organization's app credentials, which you paste into Elaichi, and there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and your Bitwarden organization is available in the chat.

### Does Bitwarden work with ChatGPT and Cursor as well as Claude?

Yes. Once Bitwarden is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Bitwarden once and every client uses that one connection.

### What can an AI agent actually do with my Bitwarden organization?

It can list and look up Bitwarden members, groups, collections, and policies, invite a new member or resend an invite, add people to groups or take them out, update a collection or a policy, import users and groups from a directory, and read the organization's event history. Ask the way you would ask a colleague: add Priya to the Finance group, who is in the Engineering group, show me last week's events. Short, specific asks work better than long paragraphs.

### Does connecting Bitwarden give the AI my passwords?

No. This Bitwarden connector works with organization administration, meaning members, groups, collections, policies, and events, not the contents of anyone's vault. Within that, access follows the person who signed in, so someone who cannot manage policies in Bitwarden cannot manage them through Claude either. Elaichi can narrow that access further with restrictions and never widens it.

### Can my team share one Bitwarden connection?

Yes. One admin connects Bitwarden in Elaichi and shares the connection with a team, and nobody else ever handles the app credentials. Each person still signs in to Elaichi as themselves, so the audit log names who invited a member or changed a policy, even over a shared Bitwarden connection.

### Can I stop an agent from deleting members or changing policies in Bitwarden?

Yes. Restrictions in Elaichi work per action, so you can restrict deleting Bitwarden members, groups, or collections, or updating policies, for a role or for one person, while leaving listing and inviting available. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Bitwarden connection when someone leaves?

Offboarding the person in Elaichi ends their access to Bitwarden through every client at once. If they set up a shared Bitwarden connection, it keeps working for everyone else on the team. Disconnecting Bitwarden once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client together.

### Does the Bitwarden MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Bitwarden is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Bitwarden?

Yes. Both let Claude, ChatGPT or Cursor use Bitwarden. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Bitwarden call.

### How is Elaichi different from Composio for Bitwarden?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Bitwarden: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 28 Bitwarden tools

Every tool below is callable through https://api.elaichi.ai/mcp once Bitwarden is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Bitwarden members** (List). List all members of a Bitwarden organization. Returns each member's id.
- **Get single Bitwarden member by ID** (Get). Retrieve a single member of a Bitwarden organization by id. Returns the member's id. Required: id.
- **Create a Bitwarden member** (Create). Create a member in Bitwarden by inviting a user to the organization. Returns the created member object including its id (the unique member identifier returned upon creation). Required:, and a MemberCreateRequestModel request body.
- **Update a Bitwarden member by ID** (Update). Update a Bitwarden organization member by id. Returns the updated member object: id plus the member's field set (attributes). Any property omitted from the body is reset, so resend existing values for properties you want to keep. Required: id.
- **Delete a Bitwarden member by ID** (Delete). Delete a Bitwarden organization member by id. Permanently removes the member from the organization; this cannot be undone, though the user's account itself remains. Returns an empty 204 response on success. Required: id.
- **List all Bitwarden groups** (List). List all groups in a Bitwarden organization. Returns group records unwrapped from the data envelope, each keyed by its string id; remaining group fields are defined upstream.
- **Get single Bitwarden group by ID** (Get). Retrieve a single group from a Bitwarden organization by id. Returns the group record keyed by its string id; remaining group fields are defined upstream. Required: id.
- **Create a Bitwarden group** (Create). Create a new group in a Bitwarden organization. Returns the created group record: id and attributes. Required: and a JSON body following Bitwarden's GroupCreateUpdateRequestModel.
- **Update a Bitwarden group by ID** (Update). Update a group in a Bitwarden organization by id. Returns the updated group record: id and attributes. Properties omitted from the body are reset, so send the full desired object. Required: id, and a JSON body following Bitwarden's GroupCreateUpdateRequestModel.
- **Delete a Bitwarden group by ID** (Delete). Permanently delete a group from a Bitwarden organization by id. This cannot be undone. Returns an empty response on success. Required: id and.
- **List all Bitwarden public collections** (List). List all collections in your Bitwarden organization. Returns collection objects including id, object, and name; listed collections do not include their associated groups. Required:.
- **Get single Bitwarden public collection by ID** (Get). Get a single Bitwarden collection by its unique id. Returns the collection object including id, object, and name. Required: id.
- **Update a Bitwarden public collection by ID** (Update). Update a Bitwarden collection by id; any request-body property omitted is reset to its existing value. Returns the updated collection object including id, object, and name. Required: id.
- **Delete a Bitwarden public collection by ID** (Delete). Permanently delete a Bitwarden collection by id. This cannot be undone. Returns an empty 200 response on success. Required: id.
- **List all Bitwarden public events** (List). List Bitwarden organization event logs, filtered by date range or actor, paged by a continuation token. Returns: object, type, itemId, collectionId, groupId, policyId, memberId, actingUserId, date, device, ipAddress. Required:. Defaults to the last 30 days when no filters are provided.
- **Bitwarden group member IDS bulk update** (Update). Update a Bitwarden group's member associations by replacing them with the supplied list of member ids. Returns an empty response body on success. Required: group_id, member_ids.
- **List all Bitwarden group member IDS** (List). List the ids of all members associated with a Bitwarden group. Returns an array of unique member id strings (UUIDs). Required: group_id.
- **Bitwarden member group IDS bulk update** (Update). Update a Bitwarden member's group associations to the supplied list of group ids, replacing the member's existing group memberships. Returns an empty 200 response on success. Required:, member_id, group_ids.
- **List all Bitwarden member group IDS** (List). Retrieve the group ids for a Bitwarden member. Returns the unique group id UUIDs for every group the member belongs to. Required:, member_id, id.
- **Create a Bitwarden member reinvite** (Create). Re-invite a member in Bitwarden by re-sending the invitation email to an organization member. Returns an empty 200 response on success. Required: member_id (the UUID identifier of the member to re-invite).
- **Create a Bitwarden organization import** (Create). Import members and groups into a Bitwarden organization from an external system. Returns the imported member record including its id. Required: plus the import request body (OrganizationImportRequestModel) describing the members and groups to import.
- **List all Bitwarden public policies** (List). List all Bitwarden enterprise policies for your organization. Returns each policy's id, type, and enabled state. Required:.
- **Update a Bitwarden public policy by ID** (Update). Update a Bitwarden enterprise policy by id, toggling it via the enabled body property. Returns the updated policy's id, type, and enabled state. Required: id = the policy type number (0 TwoFactorAuthentication, 1 MasterPassword, 2 PasswordGenerator, 3 SingleOrg, 4 RequireSso, 5 OrganizationDataOwnership, 6 DisableSend, 7 SendOptions, 8 ResetPassword, 9 MaximumVaultTimeout, 10 DisablePersonalVaultExport, 11 ActivateAutofill, ...).
- **Get single Bitwarden public policy by ID** (Get). Retrieve a Bitwarden organization policy's details by policy type. Returns the policy response for the requested type; fields vary by policy type. Required: id = the policy type number (0 TwoFactorAuthentication, 1 MasterPassword, 2 PasswordGenerator, 3 SingleOrg, 4 RequireSso, 5 OrganizationDataOwnership, 6 DisableSend, 7 SendOptions, 8 ResetPassword, 9 MaximumVaultTimeout, 10 DisablePersonalVaultExport, 11 ActivateAutofill, ...).
- **Create a Bitwarden member revoke** (Create). Revoke a member's access to the Bitwarden organization. Returns an empty 200 response on success. Required: member_id.
- **Create a Bitwarden member restore** (Create). Restore a member's access to the Bitwarden organization. Returns an empty 200 response on success. Required: member_id.
- **List all Bitwarden organization subscriptions** (List). Get the Bitwarden organization subscription details. Returns: passwordManager (seats, maxAutoScaleSeats, storage), secretsManager (seats, maxAutoScaleSeats, serviceAccounts, maxAutoScaleServiceAccounts).
- **Bitwarden organization subscriptions bulk update** (Update). Update the Bitwarden organization subscription: Password Manager seats/storage and Secrets Manager seats/service accounts. Returns an empty 200 response on success.
