Skip to main content
Glama
MSPbotsAI

bitwarden-mcp

by MSPbotsAI
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

bitwarden_invite_member

Invite a new member to your Bitwarden organization by email. Set their role, access to all collections, and optional external ID for syncing; then follow up to assign groups.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNo
emailYes
access_allNo
external_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It discloses the email invitation, the initial status value of 0 (Invited), and the prerequisite for type=4 requiring custom permissions. It also clarifies that group access is not granted by this call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a top-line summary followed by parameter details. Each sentence serves a purpose—no wasted words. The Args section is appropriately detailed given the lack of schema descriptions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description fully equips an agent to invoke the tool correctly: it explains the action, parameter semantics, role enum, and the necessary follow-up. With an output schema present, return value details are covered. It is complete for this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description explains every parameter: the role enum values for type, the meaning of access_all, and the purpose of external_id. It adds critical meaning beyond the JSON schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Invite a new member to the Bitwarden organization by email.' This is a specific verb and resource, clearly distinguishing it from sibling tools like bitwarden_list_members or bitwarden_remove_member.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly instructs to follow up with bitwarden_update_member_groups to grant vault group access, and explains that the returned member 'id' is needed for that call. This provides clear usage context and an alternative next step.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MSPbotsAI/bitwarden-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server