Connect Bitwarden to ChatGPT: Manage members, groups, and policies

If you need to connect Bitwarden to ChatGPT to manage enterprise password policies, automate user provisioning, or orchestrate group access controls, you need a Model Context Protocol (MCP) server. This server acts as the translation layer between ChatGPT's tool calls and Bitwarden's underlying REST APIs. You can either spend weeks building, hosting, and maintaining a custom MCP server to translate LLM JSON arguments into Bitwarden's highly specific payload structures, or you use a managed integration platform like Truto to dynamically generate a secure, authenticated MCP server URL.

If your team uses Claude, check out our guide on connecting Bitwarden to Claude or explore our broader architectural overview on connecting Bitwarden to AI Agents.

Giving a Large Language Model (LLM) read and write access to an enterprise password manager like Bitwarden is a massive engineering and security challenge. You have to handle complex bulk update payloads, map integer-based policy IDs to natural language intents, and enforce strict access controls. Every time a developer adds a new organizational requirement, your custom server code must be updated, redeployed, and tested.

This guide breaks down exactly how to use Truto to generate a secure, managed MCP server for Bitwarden, connect it natively to ChatGPT, and execute complex identity and access management workflows using natural language.

The Engineering Reality of the Bitwarden API

A custom MCP server is a self-hosted integration layer. While the open MCP standard provides a predictable way for models to discover tools, implementing it against Bitwarden's specific organizational API is exceptionally painful.

If you decide to build a custom MCP server for Bitwarden, you own the entire API lifecycle. Here are the specific integration challenges that break standard CRUD assumptions when working with Bitwarden:

Policy Management via Integer IDs

Unlike SaaS platforms with predictable REST endpoints (e.g., /policies/password-generator), Bitwarden policies are requested and updated using hardcoded integer IDs mapping to policy types. For example, 0 is TwoFactorAuthentication, 1 is MasterPassword, and 4 is RequireSso. If you ask an LLM to "Enable the Master Password policy", a naive MCP implementation will fail because the LLM doesn't inherently know to PUT to an endpoint using ID 1. Your MCP schemas must explicitly map these integers to human-readable descriptions in the JSON schema description fields, or the LLM will hallucinate endpoint paths.

Destructive Bulk Associations

Bitwarden handles relational mapping - like assigning members to groups - via bulk replacement rather than incremental additions. When you hit the endpoint to update a group's members, you must supply the entire array of member_ids. If an LLM decides to "add Jane to the DevOps group" and only sends Jane's ID in the payload, the Bitwarden API will happily process the request - overwriting the array and removing everyone else from the group. The MCP tool schema must include explicit prompt engineering in the property descriptions instructing the LLM to read the existing array first and append the new ID.

Rate Limiting and Empty Responses

Bitwarden aggressively rate-limits API requests to protect enterprise vaults. Truto does not retry, throttle, or apply backoff on rate limit errors. When the upstream Bitwarden API returns an HTTP 429, Truto passes that error directly to the caller. Truto normalizes upstream rate limit info into standardized headers (ratelimit-limit, ratelimit-remaining, ratelimit-reset) per the IETF spec. The caller (or the agent loop) is strictly responsible for retry and backoff logic. Furthermore, many Bitwarden write operations (like revoking a member) return empty HTTP 200 or 204 responses. Your MCP server must translate these empty bodies into success confirmations for the LLM, otherwise the model will assume the tool call failed and enter an infinite retry loop.

Creating the Bitwarden MCP Server

Truto dynamically generates MCP tools from Bitwarden's resource definitions and schema documentation. A tool only appears in the MCP server if it has a corresponding documentation entry - acting as a quality gate to ensure only well-described endpoints are exposed to ChatGPT.

You can generate the MCP server URL through the Truto dashboard or programmatically via the API.

Method 1: Via the Truto UI

For teams who want a zero-code setup, the Truto dashboard provides a point-and-click interface to generate MCP server URLs.

1. Navigate to the Integrated Accounts page for your connected Bitwarden instance.
2. Click the MCP Servers tab.
3. Click Create MCP Server.
4. Configure the server settings (name, allowed methods, tags, and expiration).
5. Click Save and copy the generated MCP server URL (e.g., https://api.truto.one/mcp/a1b2c3d4...).

Method 2: Via the Truto API

For engineering teams building programmatic agent deployments, you can create the MCP server dynamically via REST. This requires your Truto API token.

curl -X POST https://api.truto.one/integrated-account/$INTEGRATED_ACCOUNT_ID/mcp \
  -H "Authorization: Bearer $TRUTO_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Bitwarden IT Ops Agent",
    "config": {
      "methods": ["read", "write", "custom"],
      "tags": ["members", "groups", "policies"]
    },
    "expires_at": "2026-12-31T23:59:59Z"
  }'

The API returns a self-contained JSON-RPC 2.0 endpoint. The URL contains a cryptographic token that encodes the integrated account and filters, requiring no additional authentication from the client side unless explicitly configured.

{
  "id": "mcp_01j2...",
  "name": "Bitwarden IT Ops Agent",
  "url": "https://api.truto.one/mcp/a1b2c3d4e5f6..."
}

Connecting the MCP Server to ChatGPT

Once you have your Truto MCP URL, you can plug it directly into ChatGPT.

Method 1: Via the ChatGPT UI (Custom Connectors)

If you are using ChatGPT Pro, Plus, Business, Enterprise, or Education, you can add the server directly in the web interface:

1. In ChatGPT, click your profile picture and go to Settings -> Apps -> Advanced settings.
2. Enable Developer mode (MCP support requires this flag).
3. Under MCP servers / Custom connectors, click Add new server.
4. Enter a name (e.g., "Bitwarden IT Ops").
5. Paste the Truto MCP URL into the Server URL field.
6. Click Add and save your settings.

ChatGPT will immediately ping the endpoint, execute the initialization handshake, and list the available Bitwarden tools in the interface.

Method 2: Via Manual Config File (Local Setup)

If you are orchestrating local agents, custom UI wrappers, or using OpenAI's desktop application, you can connect via a standard JSON configuration file using Server-Sent Events (SSE).

Create an mcp_config.json file:

{
  "mcpServers": {
    "bitwarden-ops": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-sse",
        "--url",
        "https://api.truto.one/mcp/a1b2c3d4e5f6..."
      ]
    }
  }
}

This instructs the MCP client to use the official SSE transport adapter to proxy JSON-RPC messages over HTTP POST requests to Truto's edge routers.

Bitwarden Hero Tools

Truto's Bitwarden integration exposes dozens of endpoints as fully documented LLM tools. Here are the highest-leverage hero tools for IT and SecOps automation.

list_all_bitwarden_members

Retrieves a complete list of all users within your Bitwarden organization. The tool normalizes the pagination and returns arrays of member records, including their unique id which is required for subsequent operations.

"Get a list of all active members in our Bitwarden organization so I can cross-reference them with our HR system."

create_a_bitwarden_member

Invites a new user to the organization. The LLM must construct a request body that follows Bitwarden's schema, specifying the user's email address and initial collection access. Bitwarden handles sending the invitation email.

"Invite new.employee@example.com to Bitwarden. Do not assign them to any groups yet."

bitwarden_group_member_ids_bulk_update

Updates a Bitwarden group's member associations by replacing the current members with a newly supplied array of member IDs. Truto's auto-generated schema instructs the LLM to fetch the existing list first if it intends to append a user.

"Add member ID 9b3a-4c2d... to the Engineering group. Make sure you fetch the current members of the Engineering group first so you don't overwrite anyone."

get_single_bitwarden_public_policy_by_id

Retrieves the details of a specific enterprise policy. The LLM is provided a schema mapping policy types to integers (e.g., 1 = MasterPassword, 4 = RequireSso, 10 = DisablePersonalVaultExport).

"Check the status of the 'Require SSO' policy in our Bitwarden organization to see if it is currently enabled."

update_a_bitwarden_public_policy_by_id

Toggles an enterprise policy on or off. The LLM passes the integer ID in the path and a boolean enabled flag in the body. Returns the updated policy state.

"Turn on the 'Disable Personal Vault Export' policy to ensure departing employees cannot bulk-export corporate credentials."

create_a_bitwarden_member_revoke

Immediately cuts off a member's access to the organization without deleting their personal vault account. This is the critical kill-switch for offboarding workflows.

"Revoke access for member ID 8c2b-1a4f... immediately."

list_all_bitwarden_public_events

Fetches audit logs and event history for the organization. Can be filtered by date range or specific acting users. Crucial for security investigations and compliance reporting.

"Pull the Bitwarden event logs for the last 7 days and summarize any instances where users exported vault data."

For the complete tool inventory, request schemas, and underlying API parameters, view the Bitwarden integration page.

Workflows in Action

Once ChatGPT is armed with these tools, it can orchestrate multi-step infrastructure tasks that normally require a human navigating the Bitwarden web console.

Scenario 1: Zero-Touch Employee Offboarding

When an employee leaves, IT needs to ensure their access is fully revoked across the stack.

"Jane Doe (jane.doe@example.com) is leaving the company today. Please find her Bitwarden account, tell me what groups she is currently a member of, and then completely revoke her access to our organization."

Step-by-step execution:

1. The agent calls list_all_bitwarden_members to search the directory and find the UUID matching jane.doe@example.com.
2. The agent calls list_all_bitwarden_member_group_ids using Jane's UUID to audit her current access levels.
3. The agent calls list_all_bitwarden_groups to resolve those group UUIDs into human-readable names to report back to the user.
4. The agent calls create_a_bitwarden_member_revoke with Jane's UUID to disable her organizational access.

Result: The agent replies with a confirmation that Jane has been removed, noting that she was previously in the "Marketing" and "Contractors" groups.

sequenceDiagram
    participant User as User
    participant ChatGPT as ChatGPT
    participant MCP as Truto MCP Router
    participant API as Bitwarden API

    User->>ChatGPT: "Revoke jane.doe@example.com"
    ChatGPT->>MCP: Call list_all_bitwarden_members
    MCP->>API: GET /members
    API-->>MCP: [ { id: "uuid-123", email: "jane..." } ]
    MCP-->>ChatGPT: Member records
    ChatGPT->>MCP: Call create_a_bitwarden_member_revoke(id="uuid-123")
    MCP->>API: POST /members/uuid-123/revoke
    API-->>MCP: HTTP 200 Empty
    MCP-->>ChatGPT: Success response
    ChatGPT-->>User: "Jane Doe's access has been successfully revoked."

Scenario 2: Enforcing Enterprise Security Policies

SecOps needs to ensure baseline configurations haven't drifted.

"Audit our Bitwarden enterprise policies. Ensure that both 'Master Password' reset and 'Require SSO' are enabled. If either is disabled, turn it on and log the change."

Step-by-step execution:

1. The agent parses its internal schema to realize "Master Password" is ID 1 and "Require SSO" is ID 4.
2. The agent calls get_single_bitwarden_public_policy_by_id for ID 1. It sees enabled: true.
3. The agent calls get_single_bitwarden_public_policy_by_id for ID 4. It sees enabled: false.
4. The agent calls update_a_bitwarden_public_policy_by_id passing ID 4 and {"enabled": true} in the body.

Result: The agent replies: "Master Password reset was already enabled. Require SSO was disabled, but I have successfully turned it on to enforce compliance."

Security and Access Control

Exposing an enterprise password manager to an AI agent requires strict guardrails. Truto's MCP tokens carry embedded configuration constraints that the LLM cannot bypass.

• Method Filtering: You can restrict a Bitwarden MCP server to methods: ["read"]. The LLM can audit policies and list users, but cannot invoke create, update, or revoke operations.
• Tag Filtering: By configuring tags: ["events"], you can create a purpose-built audit agent that only has access to the list_all_bitwarden_public_events tool, isolating it from user management entirely.
• Secondary Authentication (require_api_token_auth): If enabled, possession of the MCP URL is not enough. The client must pass a valid Truto API token in the Authorization header, meaning only authenticated team members can execute tools.
• Automatic Expiration (expires_at): You can bind a TTL to the MCP server. When the ISO timestamp passes, distributed edge alarms automatically destroy the server and its KV storage footprint, preventing zombie access for temporary contractors or auditors.

Moving Beyond Point-to-Point Scripts

Writing custom Python scripts to bridge ChatGPT function calling and Bitwarden's specific API quirks is a maintenance trap. By leveraging Truto's auto-generated MCP servers, you offload the complexity of schema translation, authentication persistence, and rate-limit header normalization.

You connect the integrated account once, generate the URL, and instantly give your AI agents the exact tools they need to manage users, groups, and policies securely.