Connect Bitwarden to Claude Code

Manage an organisation's members, groups, collections, and policies. Add Toolspoke to Claude Code once and it can use 26 Bitwarden actions. Your Bitwarden credential stays in Toolspoke, and you choose which actions Claude Code may call.

Set it up in Claude Code

Three steps, the first one once for every toolkit you will ever add.

  1. Add Toolspoke to Claude Code

    Run it in your project, then /mcp to sign in

    claude mcp add --transport http toolspoke https://toolspoke.com/mcp

    The sign-in opens in your browser, and Toolspoke asks you to approve it.

  2. Install Bitwarden and connect it

    Add Bitwarden to a project in your Toolspoke workspace.

    OAuth 2.0 client credentials. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

    Client ID
    Bitwarden → Settings → Organization info → View API key. It must be the organisation key, which starts with organization., a user. key cannot reach these endpoints.
    Client secret
    Shown beside the client ID on the same screen. Regenerating it there revokes this connection.
  3. Choose what Claude Code may do

    All 26 actions start on. Switch off any of the 14 actions that change something in Bitwarden, and Claude Code gets a refusal if it tries.

What you can ask Claude Code for

A few of the Bitwarden actions that only read, so they are safe to try first.

  • Fetch one member by id, with their role, permissions, and collection access
  • List the group ids one member belongs to
  • List the organisation's groups with the collections each one grants
  • Fetch one group by id, with the collections it grants

What Claude Code can do in Bitwarden

12 actions read, 3 write and 11 delete or permanently change something.

Reads

  • List members

    List everyone in the organisation with their email, role, two-factor status, invitation status, and the collections they can reach. Call this first, every other member action takes the member id from here. Status is 0 invited, 1 accepted, 2 confirmed, 3 staged, -1 revoked; type is 0 owner, 1 admin, 2 user, 4 custom.

  • Get member

    Fetch one member by id, with their role, permissions, and collection access.

  • List member groups

    List the group ids one member belongs to. Read this before update_member_groups, which replaces the whole list rather than adding to it.

  • List groups

    List the organisation's groups with the collections each one grants. Groups are how collection access is handed out in bulk, so this is the map of who can reach what.

  • Get group

    Fetch one group by id, with the collections it grants. Read this before update_group, which replaces the whole record.

  • List group members

    List the member ids in one group. Read this before update_group_members, which replaces the whole list rather than adding to it.

  • List collections

    List the organisation's collections. Only names and ids, the groups attached to each one are not included here, so use get_collection for that. Collections hold vault items; this API never returns the items themselves.

  • Get collection

    Fetch one collection by id, including the groups that can reach it. Read this before update_collection, which replaces the whole group list.

  • List policies

    List the organisation's security policies and whether each is switched on. The cheapest call that proves the API key works, and the way to check settings such as required two-factor or single organisation. Each policy is identified by an integer type, see update_policy for the list.

  • Get policy

    Fetch one policy by its integer type, with its current settings. Read this before update_policy, which replaces the settings wholesale.

  • List events

    Read the organisation's event log, who signed in, who viewed or changed which vault item, and who altered a group or policy. With no filters it returns the last 30 days. Pass the continuationToken from a previous response to page through more than one batch.

  • Get subscription

    Read the organisation's seat counts and storage, for Password Manager and Secrets Manager. Use it to check how many seats are left before inviting anybody.

Writes

  • Reinvite member

    Send the invitation email again to a member who has not accepted yet. Grants nothing new, the invitation and its access were already decided by invite_member.

  • Revoke member

    Suspend a member's access without removing them from the organisation. This is the safe direction, it takes access away and restore_member puts it back, so it is the right first move when an account may be compromised.

  • Create group

    Create a group. A new group has no members, so it grants nobody anything until update_group_members adds people to it, that call is the one that hands out access.

Deletes or permanently changes

  • Invite member

    Invite somebody to the organisation, which emails them and begins granting them access to the collections named here. Classified destructive rather than write because it hands a person outside the workspace a route into shared credentials, and the email cannot be recalled. Type is 0 owner, 1 admin, 2 user, 4 custom.

  • Update member

    Replace a member's role, permissions, groups, and collection access. This is a full replacement: anything left out is reset, so read get_member first and send back everything that should survive. Destructive because it can promote somebody to owner, or widen which shared credentials they can read.

  • Update member groups

    Replace the set of groups a member belongs to. Groups carry collection access, so this changes which shared credentials the person can read. Sending a shorter list removes them from the groups left out, read list_member_groups first.

  • Restore member

    Give a revoked member their access back. Destructive because it re-opens somebody's route into shared credentials, which is the half of the revoke/restore pair that grants rather than removes.

  • Delete member

    Remove a member from the organisation. Bitwarden's own documentation says this cannot be undone; their personal account survives but their membership, and anything only they could reach through it, does not. Use revoke_member when the intent is to suspend somebody rather than to erase the membership.

  • Update group

    Replace a group's name and the collections it grants. Every member of the group gains or loses access accordingly, and anything left out is reset, read get_group first and send back what should survive.

  • Update group members

    Replace the set of members in a group, which is how collection access is granted or taken away in bulk. Sending a shorter list removes everybody left out, read list_group_members first.

  • Delete group

    Delete a group. Everyone in it loses whatever access the group granted, and the grouping itself is gone, rebuilding it means naming every member and collection again.

  • Update collection

    Replace which groups can reach a collection. This decides who can read the credentials inside it, and anything left out is removed, read get_collection first. The Public API cannot create or read collection contents, only re-point access at them.

  • Delete collection

    Delete a collection and every vault item inside it. This is the most damaging call in the connector: the credentials it holds go with it, and the Public API offers no way to read them first or put them back.

  • Update policy

    Switch a security policy on or off. Destructive because switching one off weakens the organisation for everybody at once, turning off type 0 stops requiring two-factor authentication on an account that holds shared credentials. Types: 0 two-factor authentication, 1 master password, 2 password generator, 3 single organisation, 4 require SSO, 5 organisation data ownership, 6 disable Send, 7 Send options, 8 account recovery, 9 maximum vault timeout, 10 disable personal vault export, 11 activate autofill, 12 automatic app log-in, 13 free families sponsorship, 14 remove unlock with PIN, 15 restricted item types, 16 URI match defaults, 17 autotype default, 18 automatic user confirmation, 19 block claimed-domain account creation, 20 organisation user notification, 21 Send controls, 22 fill assist.

Bitwarden in Claude Code: questions

Does Claude Code see my Bitwarden credential?

No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.

Can I stop Claude Code from changing things in Bitwarden?

Yes. Each of the 26 actions can be switched off for a project. Turn off the 14 that change something and Claude Code can only read.

Will 26 actions crowd Claude Code's context?

No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the Bitwarden action it needs when it needs it. Adding more toolkits does not add more tools to its list.

Can I add it once for every project?

Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.

What does it cost?

Tool calls are free on every plan, and a Bitwarden call does not run in a sandbox, so it bills nothing.

Try Bitwarden in Claude Code

Free to start, and tool calls cost nothing on any plan.