Skip to main content
Glama
kefapps

mcp-1password

by kefapps

Related Servers

Alternatives to mcp-1password

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server enabling AI agents to use secrets (API keys, tokens) via encrypted vault, executing HTTP/shell/SSH actions server-side while never exposing secret values to the AI.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that lets AI agents call APIs without ever seeing the credentials, using a local encrypted vault and per-secret allowlist policies for HTTP requests and subprocess environment variables.
      1
      AGPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides secure access to 1Password secrets and item management through the 1Password CLI. It enables MCP clients like Claude and Cursor to read, create, edit, and delete password vault items with biometric authentication handled by the 1Password desktop app.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for secure AI agent access to Bitwarden/Vaultwarden vaults with BYOK, exposing tools to list items, reveal secrets via encrypted Sends, get TOTP codes, and save credentials.
      7
      50 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for secure, just-in-time secret retrieval from 1claw vault and malicious content inspection, enabling AI agents to access secrets and security analysis.
      1
      1,290 npm
      2
      MIT

    TDQS

    C2.9/5.0

    Scored across 16 tools

    Disambiguation3/5

    Most tools target distinct resources, but `vault_get` and `vault_permissions_get` overlap on accessor permissions, and `password_read`, `secret_reveal`, and `environment_reveal_variable` all concern retrieving secret values with similar caveats. The detailed descriptions clarify intended use, but an agent could still confuse reveal paths or pick the wrong secret-reading tool.

    Naming Consistency4/5

    The set mostly follows a consistent snake_case `resource_verb` pattern (`vault_list`, `password_read`, `item_search`), and verbs are clear. Minor deviations like `sdk_capabilities` and `op_session_status` are noun-like informational tools, and `item_request_list` is a compound noun/verb, but these are understandable.

    Tool Count4/5

    16 tools is slightly above the typical 3–15 range, but the server covers several distinct areas: environment variables, passwords, vaults, groups, permissions, and item metadata. Each tool has a specific job, so the count is reasonable rather than bloated.

    Completeness2/5

    The set has significant gaps: plaintext reveal tools are disabled and the referenced `op_script_run`/`item_request_create` tools are absent, leaving agents with dead ends when they need to consume or create secrets. There is also no item/vault/environment write or update surface, so lifecycle coverage is limited.

    Maintenance

    ActivityStale
    ResponsivenessNo issues