Skip to main content
Glama
icoretech

Warden MCP Server

by icoretech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create Login

keychain_create_login

Create a vault login item with username, password, TOTP, and URIs, including custom fields and attachments, with folder or collection scoping and redacted summary output.

Instructions

Create a login item with username/password/TOTP/URI data. Use this for website or app credentials instead of a secure note, card, or identity. Accepts custom fields and attachments, supports folder/organization/collection scoping, and returns a redacted item summary by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDisplay name for the login item.
totpNoTOTP secret or otpauth value for the login item.
urisNoURI entries to store or update on the login item.
notesNoOptional free-form notes for the login item.
fieldsNoCustom fields to store on the item. Hidden fields are redacted in summaries.
favoriteNoMark the item as a favorite when true.
folderIdNoPersonal folder id, not an organization collection id.
passwordNoPassword to store on the login item.
usernameNoLogin username or email address.
attachmentsNoAttachments to add to the item.
collectionIdsNoBitwarden collection ids, not folder ids.
organizationIdNoBitwarden organization id; used for org-scoped collection operations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed22 schema fields changedv0.2.19
    • addedInput schema / properties / attachments / description
      Added value: +"Attachments to add to the item."
    • addedInput schema / properties / attachments / items / description
      Added value: +"Attachment file payload to add to the item."
    • addedInput schema / properties / attachments / items / properties / contentBase64 / description
      Added value: +"Base64-encoded file bytes, not a filesystem path."
    • addedInput schema / properties / attachments / items / properties / filename / description
      Added value: +"Visible attachment or send filename stored in Bitwarden metadata."
    • addedInput schema / properties / collectionIds / description
      Added value: +"Bitwarden collection ids, not folder ids."
    • addedInput schema / properties / favorite / description
      Added value: +"Mark the item as a favorite when true."
    • addedInput schema / properties / fields / description
      Added value: +"Custom fields to store on the item. Hidden fields are redacted in summaries."
    • addedInput schema / properties / fields / items / description
      Added value: +"Custom field stored on the item."
    • addedInput schema / properties / fields / items / properties / hidden / description
      Added value: +"Hide the field value in summaries when true."
    • addedInput schema / properties / fields / items / properties / name / description
      Added value: +"Custom field name stored on the item."
    • addedInput schema / properties / fields / items / properties / value / description
      Added value: +"Custom field value stored on the item."
    • addedInput schema / properties / folderId / description
      Added value: +"Personal folder id, not an organization collection id."
    • addedInput schema / properties / name / description
      Added value: +"Display name for the login item."
    • addedInput schema / properties / notes / description
      Added value: +"Optional free-form notes for the login item."
    • addedInput schema / properties / organizationId / description
      Added value: +"Bitwarden organization id; used for org-scoped collection operations."
    • addedInput schema / properties / password / description
      Added value: +"Password to store on the login item."
    • addedInput schema / properties / totp / description
      Added value: +"TOTP secret or otpauth value for the login item."
    • addedInput schema / properties / uris / description
      Added value: +"URI entries to store or update on the login item."
    • addedInput schema / properties / uris / items / description
      Added value: +"URI entry with match semantics for a login item."
    • addedInput schema / properties / uris / items / properties / match / description
      Added value: +"URI match semantics: domain, host, startsWith, exact, regex, or never; aliases and numeric values are normalized."
    • addedInput schema / properties / uris / items / properties / uri / description
      Added value: +"URI value to store on the login item."
    • addedInput schema / properties / username / description
      Added value: +"Login username or email address."
  2. Addedv0.1.20

TDQS

A4/5.0
Behavior3/5

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

The description adds that the tool returns a redacted item summary by default, which supplements the annotations (readOnlyHint=false, destructiveHint=false). No contradictions. However, it does not disclose other behavioral aspects like permission requirements or side effects, so additional context beyond annotations is limited.

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 concise (two sentences) and well-structured: first sentence states the core action and data types, second provides usage guidance and lists additional capabilities. No unnecessary words.

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

Completeness4/5

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

Given the complexity (12 parameters, no output schema), the description covers the primary inputs and return behavior. It lacks details on error handling or validation, but for a creation tool with well-documented schema, it is fairly complete.

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

Parameters3/5

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

The input schema has 100% coverage with descriptions for all 12 parameters. The description does not add significant additional meaning beyond what the schema provides, justifying the baseline score of 3.

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 clearly states the tool creates a login item with specific data types (username, password, TOTP, URI) and explicitly distinguishes it from other item types like secure note, card, or identity. This provides clear purpose and differentiation from siblings.

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

Usage Guidelines4/5

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

The description explicitly advises using this for website/app credentials instead of other item types, providing clear context for when to use the tool. It lacks explicit guidance on when not to use it, but the positive direction is strong.

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

Deploy Server

Other Tools