Connect Claude to Bitwarden

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.

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

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

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

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

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.

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

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.

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

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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

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

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.