1Password MCP integration for AI agents.
Connect AI agents to 1Password through 6 structured actions, including get health, get item, and get vault. Review authentication, inputs, workflows, and saf…
- ACTION CONTRACTS
- 6
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the 1Password integration exposes
The 1Password Agent App exposes 6 provider-backed actions for security and productivity work. Its current contract lets an authorized agent get health details for the configured 1password connect server, get one full 1password item by vault uuid and item uuid, and get details for one 1password vault by uuid. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected 1Password account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real 1Password capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_healthREADGet health details for the configured 1Password Connect Server.
get_itemREADGet one full 1Password item by vault UUID and item UUID.
INPUTS: vaultId / itemId
get_vaultREADGet details for one 1Password vault by UUID.
INPUTS: vaultId
list_activityREADList 1Password Connect activity events visible to the access token.
INPUTS: limit / offset
list_itemsREADList item overviews in one 1Password vault.
INPUTS: vaultId / filter
list_vaultsREADList 1Password vaults available to the connected Connect access token.
INPUTS: filter
INPUT CONTRACTS
Know what the action needs before it runs.
get_item
vaultIdREQUIRED- The 1Password vault UUID.
itemIdREQUIRED- The 1Password item UUID.
get_vault
vaultIdREQUIRED- The 1Password vault UUID.
list_activity
limitOPTIONAL- Maximum number of activity events to return.
offsetOPTIONAL- Zero-based activity event offset.
list_items
vaultIdREQUIRED- The 1Password vault UUID.
filterOPTIONAL- A SCIM-style filter for item titles or tags, such as title eq "Example Item".
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Health
Get health details for the configured 1Password Connect Server. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_healthVerify with Get Item
Get one full 1Password item by vault UUID and item UUID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_itemSAFETY BOUNDARY
Operate 1Password with explicit limits
- Authorize 1Password with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned 1Password data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in 1Password rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the 1Password task completed successfully.
CONNECTION MODEL
API key
1Password Connect access token sent with the Authorization: Bearer header. Create or copy it from your 1Password Connect Server setup: https://developer.1password.com/docs/connect/get-started.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 6
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by 1Password.