Skip to main content
Glama
MSPbotsAI

bitwarden-mcp

by MSPbotsAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AUTH_MODENoAuthentication mode: 'env' or 'gateway'gateway
MCP_HTTP_HOSTNoHTTP server bind address0.0.0.0
MCP_HTTP_PORTNoHTTP server port8080
MCP_TRANSPORTNoTransport mode: 'stdio' or 'http'stdio
BITWARDEN_API_URLNoPublic API base URLhttps://api.bitwarden.com
BITWARDEN_CLIENT_IDNoOrganization API Key Client ID
BITWARDEN_IDENTITY_URLNoIdentity token endpoint base URLhttps://identity.bitwarden.com
BITWARDEN_CLIENT_SECRETNoOrganization API Key Client Secret

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
bitwarden_list_membersA

List all members of the Bitwarden organization.

Each member's "status" field is 0=Invited, 1=Accepted, 2=Confirmed.

bitwarden_get_memberA

Get a single organization member's details.

    Args:
        member_id: The member's UUID (see bitwarden_list_members).
bitwarden_invite_memberA

Invite a new member to the Bitwarden organization by email.

    The invited member receives an email invitation; their "status" starts
    at 0 (Invited) until they accept it. To grant access to specific vault
    groups, follow up with bitwarden_update_member_groups once the invite
    succeeds (the returned member "id" is needed for that call).

    Args:
        email: Email address to invite.
        type: Organization role — 0=Owner, 1=Admin, 2=User (default, i.e. regular
            Member), 3=Manager, 4=Custom (requires the organization to have
            custom permissions enabled).
        access_all: Whether the member gets access to all collections (default: False).
        external_id: Optional external identifier (e.g. from an HR/IdP system) for syncing.
bitwarden_reinvite_memberA

Resend the invitation email to a member who hasn't accepted it yet.

    Args:
        member_id: The member's UUID (see bitwarden_list_members).
bitwarden_remove_memberA

Remove a member from the Bitwarden organization.

    Args:
        member_id: The member's UUID (see bitwarden_list_members).
bitwarden_list_member_groupsA

List the vault group IDs a member currently belongs to.

    Args:
        member_id: The member's UUID (see bitwarden_list_members).
bitwarden_update_member_groupsA

Set which vault groups a member belongs to — this is the "group invitation" action.

    IMPORTANT: this REPLACES the member's entire group list, it does not append.
    To add the member to a group without losing existing memberships, first call
    bitwarden_list_member_groups, merge the new group id(s) into that list, then
    pass the full merged list here.

    Args:
        member_id: The member's UUID (see bitwarden_list_members).
        group_ids: Full list of vault group UUIDs the member should belong to
            after this call (see bitwarden_list_groups for available group IDs).
bitwarden_list_groupsA

List all vault groups in the Bitwarden organization.

bitwarden_create_groupA

Create a new vault group in the Bitwarden organization.

    Use the returned group "id" with bitwarden_update_member_groups to invite
    members into it.

    Args:
        name: Name of the group to create.
        access_all: Whether the group gets access to all collections (default: False).
        external_id: Optional external identifier (e.g. from an HR/IdP system) for syncing.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 9 tools

Disambiguation5/5

Each tool targets a distinct resource and action: group listing/creation, member listing/retrieval/invitation/removal, and member-group membership operations. There is no overlap that could cause misselection; list vs. get and list vs. update are clearly read vs. write.

Naming Consistency5/5

All tool names follow a consistent 'bitwarden_verb_noun' pattern, using snake_case throughout. The verbs (list, get, invite, reinvite, remove, update, create) are clear and aligned with the noun, making the pattern predictable and easy to follow.

Tool Count5/5

Nine tools is well within the ideal range for a focused server. Each tool covers a meaningful operation for Bitwarden organization member and group management, with no redundant or extraneous utilities.

Completeness4/5

The core workflows for managing members and their group memberships are covered, including invite, remove, list, get, and group assignment. Minor gaps exist: no update or delete for groups, and no separate tool to update a member's role/access_all after creation, but these are workaroundable and do not severely hinder the primary use case.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources