How to connect 1password to OpenClaw
Connect 1password to OpenClaw with ClawLink: paste your 1password key once and 6 tools work from chat. No MCP server to run, nothing stored on your machine.
1passwordAPI KEYMCPPassword manager and digital vault for secure credential storage and team collaboration.. Once connected, OpenClaw can read and act on 1password from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to 1password access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical 1password setup: install one ClawHub skill, connect 1password in the browser, and OpenClaw can call real 1password actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to 1password.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect 1password
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with 1password?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect 1password in the ClawLink dashboard — paste your 1password API key once.
Verify the connection by asking OpenClaw:
Use 1password to 1password get item and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once 1password is connected in the dashboard, that agent calls the same 6 1password tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
1password MCP for OpenClaw
Looking for a 1password MCP server for OpenClaw? ClawLink connects 1password to OpenClaw and exposes 6 1password tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes 1password integration works the same way.
What the OpenClaw 1password integration can do
6 1password tools are ready for OpenClaw once the account is connected. The 5 below are the ones people reach for most; your agent can call all 6.
5 of 6 1password tools for OpenClaw
| Tool | What it does |
|---|---|
1password get item _1password_get_item | Retrieves a specific item from a vault, including all fields and secrets |
1password list items _1password_list_items | Lists all items in a given vault |
1password list vaults _1password_list_vaults | Lists all vaults the service account has access to |
1password create item _1password_create_item | Creates a new item in a 1Password vault |
1password update item _1password_update_item | Updates an existing item's title or field values |
Try it: find the 1password tool you need
Browse the 5 1password tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use 1password to 1password get item and walk me through the result in plain English.
Use 1password to 1password list items and walk me through the result in plain English.
Use 1password to 1password list vaults and walk me through the result in plain English.
Use 1password to 1password create item and walk me through the result in plain English.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want 1password working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the 1password API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected 1password account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for 1password. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right 1password actions to the runtime in a format your agent can reliably use. | 6 tools for 1password are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes 1password to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect 1password in the browser, and the 6 tools above work from chat. There is no SDK and no config file, and the 1password key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the 1password skill but can't call the tools
The ClawHub skill teaches OpenClaw about 1password, but the calls run through the ClawLink plugin and your connected account. Make sure 1password is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect 1password from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling 1password tools
1password tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every 1password call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
1password returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for 1password has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw 1password integration?
Yes. ClawLink is the fastest way to connect OpenClaw to 1password: link your 1password account once in the browser and OpenClaw can call the 1password API through 6 ready-made tools — no custom code or token handling.
How do I add 1password to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink 1password skill from ClawHub, then you click Connect in the dashboard to authorize 1password. OpenClaw calls the tools from the next message — no config files, and the 1password key you paste is stored server-side instead of in your environment.
How long does it take to connect 1password to OpenClaw?
About two minutes. Sign in, click Connect next to 1password in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring 1password up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want 1password working from chat.
OpenClaw installed the 1password skill but can't call the tools
The ClawHub skill teaches OpenClaw about 1password, but the calls run through the ClawLink plugin and your connected account. Make sure 1password is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
Connect GitHub
Manage repositories, issues, pull requests, and workflows
OpenClaw PagerDuty integration
Manage incidents, on-call schedules, and services
SafetyCulture
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.