Skip to main content
Glama
lwsinclair

onepassword-mcp-server

by lwsinclair
OverviewSchemaRelated ServersScoreDiscussions
Local

Project Note: ⚠️ This MCP server is a proof of concept and is intended for educational purposes only. It utilizes the 1Password Python SDK to securely retrieve credentials from your 1Password account and provides them via the MCP Python SDK to Agentic AI for use in its operations. ⚠️

Quick Start

Installing via Smithery

To install 1Password Credential Retrieval Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @dkvdm/onepassword-mcp-server --client claude

Prerequisites

  • Python 3.11 or higher

  • uv (fast Python package installer): pip install uv

  • Install packages: uv sync

  • Create a vault within 1Password named AI, and add the items you want to use.

  • Create a service account and give it the appropriate permissions in the vaults where the items you want to use with the SDK are saved.

  • Provision your service account token, and configure clients like Claude Desktop to connect to this server. Add the following structure to the client's configuration (e.g., claude_desktop_config.json), adjusting the path and environment variables as needed:

// Example for Claude Desktop config
{
  "mcpServers": {
    "1Password": {
      "command": "uv",
      "args": [
        "run",
        "--with",
        "mcp[cli]",
        "--with",
        "onepassword-sdk",
        "mcp",
        "run",
        "/your/dir/here/onepassword-mcp-server/server.py" // Change this path
      ],
      "env": {
        "OP_SERVICE_ACCOUNT_TOKEN": "INSERT_KEY_HERE" // Insert 1Password Service Account Token
      }
    }
  }
}

  • Launch Claude and try a prompt such as "Get 1Password credentials for ticktick.com" (based on item name)

Automate Browser with 1Password and Browser-Use MCP

Install mcp-browser-use and configure both MCP servers as such:

// Example for Claude Desktop config
{
  "mcpServers": {
    "1Password": {
      "command": "uv",
      "args": [
        "run",
        "--with",
        "mcp[cli]",
        "--with",
        "onepassword-sdk",
        "mcp",
        "run",
        "/your/dir/here/onepassword-mcp-server/server.py"
      ],
      "env": {
        "OP_SERVICE_ACCOUNT_TOKEN": "INSERT_KEY_HERE"
      }
    },
    "browser-use": {
      "command": "uv",
      "args": [
        "--directory",
        "/your/dir/here/mcp-browser-use",
        "run",
        "mcp-server-browser-use"
      ],
      "env": {
        "MCP_USE_OWN_BROWSER": "true",
        "CHROME_CDP": "http://127.0.0.1:9222",
        "ANTHROPIC_API_KEY": "INSERT_KEY_HERE",
        "PYTHONIOENCODING": "utf-8",
        "PYTHONUNBUFFERED": "1",
        "PYTHONUTF8": "1"
      }
    }
  }
}

Available Tools

1 tool
get_1password_credentialsC

Get 1Password credentials for a given site.

ParametersJSON Schema
NameRequiredDescriptionDefault
item_nameYes

TDQS

C2.7/5.0
Behavior2/5

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

The description does not disclose any behavioral traits such as what the credentials contain (e.g., username, password, other fields), whether multiple results are returned, or any authentication requirements. With no annotations, this is a significant gap.

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

Conciseness4/5

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

The description is a single concise sentence, front-loaded with the key action. However, given the lack of detail, it could be expanded slightly without harming conciseness.

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

Completeness2/5

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

The description fails to provide essential context such as return format (what credentials are returned), error conditions, or prerequisites. For a simple tool with one parameter, this is inadequate.

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

Parameters2/5

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

The parameter item_name is not described in the schema (0% coverage). The description mentions 'a given site' but does not explain what item_name represents (e.g., item name, site name, URL). It adds minimal additional meaning beyond the schema's title.

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

Purpose4/5

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

The description 'Get 1Password credentials for a given site' clearly states the verb (Get) and resource (credentials) and specifies the scope (for a site). However, 'site' is ambiguous and could be clarified as a 1Password item or website URL.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. Since there are no listed sibling tools, the description should at least indicate common use cases or prerequisites, which it does not.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev0.1.0
    • First observedget_1password_credentials
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3/5.0
Disambiguation5/5

Only one tool exists, so there is no ambiguity or confusion with other tools.

Naming Consistency5/5

The single tool follows a clear verb_noun pattern using snake_case, which is consistent.

Tool Count3/5

With just one tool, the server feels thin for most use cases, but it may be acceptable for a very narrow purpose.

Completeness2/5

Only a read operation is provided; missing create, update, delete, or search capabilities for a comprehensive credential management tool.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • MCP Vaultwarden Server

    fkom13
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI agents and automation scripts to securely interact with self-hosted Vaultwarden instances through the Bitwarden CLI, automatically managing vault sessions and providing tools to read, create, update, and delete secrets programmatically.
    16
    1
    MIT

  • agent-auth

    ex-nihilo-labs
    A
    license
    Not graded
    quality
    D
    maintenance
    Zero-knowledge credential injection for AI agents. Your agent authenticates to websites and APIs without ever seeing a password, TOTP code, or API key.
    6
    1
    MIT

  • 1Password MCP Server

    CakeRepository
    A
    license
    A
    quality
    A
    maintenance
    Connects MCP-compatible AI clients to 1Password vaults via a Service Account, enabling password management and vault operations through natural language.
    15
    405
    20
    Apache 2.0

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/lwsinclair/onepassword-mcp-server'

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