Onepassword Agent MCP server

1Password Agent MCP

Local MCP access to approved 1Password items and profile data for AI agents.

npm package · setup guide · security model · uninstall guide

Agents receive encrypted local handles, not plaintext 1Password secrets. At the moment of copy or paste, the MCP resolves the selected field locally through the 1Password CLI and sends it to the OS clipboard or active app.

The repo contains no personal 1Password data. Every install connects to that user's own 1Password CLI and local approval policy.

Not affiliated with or endorsed by 1Password.

How It Works

1. Create a dedicated 1Password vault named MCPVAULT.
2. Copy or move selected logins, passwords, API credentials, credit cards, secure notes, or other supported items from your normal vaults into MCPVAULT.
3. Approve exact MCPVAULT fields for specific websites.
4. Connect Claude Code, Codex, GitHub Copilot, or another MCP client.
5. The agent can paste approved fields without seeing the plaintext in its response.

The MCP tools only expose approved fields from the configured agent vault. The local profile-data section can also expose user-entered values such as email, phone, address, name, and company.

Quick Start

Install from npm:

npm install -g onepassword-agent-mcp

Run the friendly installer. It detects supported MCP clients, shows what it found, and asks before changing their user configuration. On macOS it separately offers the optional visible menu-bar shortcut:

onepassword-agent-mcp install

Or install from GitHub:

npm install -g github:gambadio/onepassword-agent-mcp

Prefer explicit commands? Check your setup and connect clients manually:

onepassword-agent-mcp doctor

Connect every detected MCP client with one command:

onepassword-agent-mcp setup all --apply

Start the local console:

onepassword-agent-mcp admin

Open:

http://127.0.0.1:7319

Full walkthrough: docs/USER_GUIDE.md

Uninstall guide: docs/UNINSTALL.md

Does It Always Run?

No. Installing the npm package itself adds commands only. It does not install a launch agent, daemon, background service, startup item, browser extension, or hidden resident process.

• onepassword-agent-mcp admin runs the local approval console only while that terminal process is alive.
• onepassword-agent-mcp mcp is a stdio MCP server. MCP clients such as Claude Code, Codex, or VS Code launch it as a child process when they need it.
• onepassword-agent-mcp setup ... --apply only writes MCP client configuration. Existing JSON files are backed up before a merge.
• The optional macOS menu-bar companion is installed only when you explicitly choose it. Its icon is visible whenever it is running.
• Launch at login is a separate choice and is off by default. Even when enabled, the visible menu-bar app does not start the admin server until you choose Open Admin Console.
• Restarting the computer does not auto-start this project unless you enabled the optional menu-bar login item or another app starts an MCP client that then launches the stdio server.
• Persistent local state is limited to approvals and the local encryption key in ~/.onepassword-mcp.

You can see this explanation any time:

onepassword-agent-mcp runtime

Optional Mac Menu Bar

On macOS, the guided installer can add a clearly labeled 1P item to the menu bar. You can also enable it later under Mac Menu Bar Shortcut in the local admin page.

Shortened. The full README is on GitHub.