home / skills / composiohq / awesome-claude-skills / bitwarden-automation

bitwarden-automation skill

safe

/bitwarden-automation

This skill helps automate Bitwarden tasks using Composio Rube MCP by discovering tools first and managing connections.

npx playbooks add skill composiohq/awesome-claude-skills --skill bitwarden-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: bitwarden-automation
description: "Automate Bitwarden tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Bitwarden Automation via Rube MCP

Automate Bitwarden operations through Composio's Bitwarden toolkit via Rube MCP.

**Toolkit docs**: [composio.dev/toolkits/bitwarden](https://composio.dev/toolkits/bitwarden)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Bitwarden connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bitwarden`
- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas

## Setup

**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bitwarden`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. Confirm connection status shows ACTIVE before running any workflows

## Tool Discovery

Always discover available tools before executing workflows:

```
RUBE_SEARCH_TOOLS
queries: [{use_case: "Bitwarden operations", known_fields: ""}]
session: {generate_id: true}
```

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

## Core Workflow Pattern

### Step 1: Discover Available Tools

```
RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Bitwarden task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["bitwarden"]
session_id: "your_session_id"
```

### Step 3: Execute Tools

```
RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"
```

## Known Pitfalls

- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS`
- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools
- **Schema compliance**: Use exact field names and types from the search results
- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`)
- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows
- **Pagination**: Check responses for pagination tokens and continue fetching until complete

## Quick Reference

| Operation | Approach |
|-----------|----------|
| Find tools | `RUBE_SEARCH_TOOLS` with Bitwarden-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bitwarden` |
| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs |
| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` |
| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` |

---
*Powered by [Composio](https://composio.dev)*

Overview

This skill automates Bitwarden tasks by driving Composio’s Bitwarden toolkit through Rube MCP. It orchestrates discovery, connection management, and tool execution so agents can perform vault queries, item creation, updates, and bulk operations reliably. The workflow emphasizes always discovering current tool schemas before running actions.

How this skill works

First, it calls RUBE_SEARCH_TOOLS to retrieve available Bitwarden tool slugs and their exact input schemas. Next, it verifies or establishes an active Bitwarden connection via RUBE_MANAGE_CONNECTIONS. Finally, it executes actions using RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk work), passing schema-compliant arguments, a session_id, and a memory object.

When to use it

Automating vault reads, creates, updates, or deletes in Bitwarden from an agent workflow
Running bulk password or secrets operations across many items using remote workbench
Integrating Bitwarden actions into multi-step agent flows that require session state
When you need programmatic, repeatable credential management from Composio toolkits

Best practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and full input schemas
Verify connection status with RUBE_MANAGE_CONNECTIONS and complete auth flows until ACTIVE
Include the memory parameter (even if {}) and reuse session_id for the workflow
Follow the exact field names, types, and pagination tokens returned by tool schemas
Generate a new session_id for distinct workflows and handle pagination until complete

Example use cases

Query all login items that match a domain and export selected fields into a report
Create or update multiple credential items in bulk using RUBE_REMOTE_WORKBENCH
Rotate a password: fetch the item, generate a new secret, update the vault entry
Automate onboarding: create shared credentials and assign collections for a new user

FAQ

Do I need API keys to use Rube MCP?

No API keys are required; add https://rube.app/mcp as an MCP server in your client configuration to reach Rube MCP.

What if tool schemas change?

Always call RUBE_SEARCH_TOOLS before executing. Do not hardcode tool slugs or argument shapes—use the returned schema and recommended execution plan.