Connectors · Identity & security

1Password Events API MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to 1Password Events API and the rest of your systems. It gives your agent 9 1Password Events API actions (9 reads and 0 writes) and holds the 1Password Events API credential itself, so the agent never does. It paces 1Password Events API's limits and records every call.

Connect 1Password Events API free See pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp

9actionsin one signed file
9readlook, never change
0writecreate and update
0wait for a yesdestructive, confirmed first

Set up

Connect 1Password Events API in three steps.

01
Add actionlake to Claude.
Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
https://connect.actionlake.com/mcp
02
Connect 1Password Events API.
Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.
- bearer_token1Password Events API bearer token: 1Password.com > Integrations > Events Reporting > your integration > issue token
- regionYour 1Password Events API region
```
account { op: "connections.requirements", service: "onepassword_events" }
# free: exactly what to paste, and what is found for you
```
03
Make the first call. Check before a write.
Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.
```
do    { action: "onepassword_events.audit_events.list" }# list audit events · read · 1 upstream call
```

1Password Events API at a glance

Sign-in: Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide: bearer_token
Setup fields: region
Limits we pace to: 600 calls a minute and 30,000 an hour, per connection
API covered: Events API 1.4.1 (v1/v2) and 3.0.0 beta (v3 audit events)events.
Built from: 1Password Events API's documentation, read 23 October 2026i.1password.com 1password.dev 1password.dev
Service file: Version 1.0.0, signed (Ed25519)
Cached reads: 7 of 9 reads, for up to 5 minutes; a write clears what it affects
Data: Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in 1Password Events API.

9 actions in 1 area. Every one carries its effect, so a key can allow the reads and hold the rest.

9readlook, never change
0writecreate and update
0destructivewait for a confirmation

Events
9
9 read · 0 write · 0 destructive
List audit events · List audit events (v1) · List audit events (v3 beta) · Introspect the Events API token

Top actions

The 1Password Events API API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 4 of 1Password Events API's 4 action names are shared with at least one other connector, so an agent learns them once.

Action	What it does	Effect	Same name in
`onepassword_events.audit_events.list`List audit events	Actions performed by team members in the account: vault, item, group, user and settings changes (v2 events).	read	`identity.audit_event.list`51 connectors
`onepassword_events.audit_events.list_v1`List audit events (v1)	Audit events in the version 1 shape.	read	`identity.audit_event.list`51 connectors
`onepassword_events.token.introspect`Introspect the Events API token	Check the bearer token: its uuid, issue time, account and which event features it can read.	read	`identity.api_key.get`66 connectors
`onepassword_events.token.introspect_v1`Introspect the Events API token (v1)	Version 1 introspection: the token's UUID, IssuedAt and Features.	read	`identity.api_key.get`66 connectors
`onepassword_events.item_usages.list`List item usages	Each use of an item stored in a shared vault: who, which item and vault, what action, from where (v2 events).	read	`security.audit_log.list`69 connectors
`onepassword_events.item_usages.list_v1`List item usages (v1)	Item usage events in the version 1 shape.	read	`security.audit_log.list`69 connectors
`onepassword_events.sign_in_attempts.list`List sign-in attempts	Successful and failed attempts to sign in to the 1Password account (v2 events).	read	`identity.sign_in_event.list`7 connectors
`onepassword_events.sign_in_attempts.list_v1`List sign-in attempts (v1)	Sign-in attempt events in the version 1 shape.	read	`identity.sign_in_event.list`7 connectors

Try it

Prompts to paste into Claude.

Each one names the 1Password Events API actions it will call, so you know what it reads and what it changes before you send it.

Readread
List audit events in 1Password Events API and tell me what stands out.
callsonepassword_events.audit_events.list

Governance for 1Password Events API

Every write can wait for a yes.

None of 1Password Events API's actions is destructive. A key can still be held to reads, capped, and set so a person confirms every write.

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

a key for this connector

account {  op: "keys.create", name: "onepassword-events-agent",  allowed_actions: ["onepassword_events.*"], cap_calls: 2000,  confirm_policy: "human_for_writes"}

Illustrative. Scoped to 1Password Events API only, capped at 2,000 upstream calls, every write confirmed.

Cost

What 1Password Events API costs on actionlake.

Every 1Password Events API action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call 1Password Events API refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

1upstream call per actionall 9 1Password Events API actions
9actions pageeach page of a long list is one call
7reads can be cacheda cache hit costs nothing
100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every 1Password Events API action.

9 actions by area: the id your agent calls, what it does, and its effect.

Events9

onepassword_events.audit_events.listList audit eventsread
onepassword_events.audit_events.list_v1List audit events (v1)read
onepassword_events.audit_events.list_v3List audit events (v3 beta)read
onepassword_events.item_usages.listList item usagesread
onepassword_events.item_usages.list_v1List item usages (v1)read
onepassword_events.sign_in_attempts.listList sign-in attemptsread
onepassword_events.sign_in_attempts.list_v1List sign-in attempts (v1)read
onepassword_events.token.introspectIntrospect the Events API tokenread
onepassword_events.token.introspect_v1Introspect the Events API token (v1)read

Questions

The 1Password Events API MCP server, answered.

Is there a 1Password Events API MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 9 1Password Events API actions, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by 1Password Events API.

What do I need to connect 1Password Events API?

1Password Events API bearer token: 1Password.com > Integrations > Events Reporting > your integration > issue token. Plus your region. The free call account { op: "connections.requirements", service: "onepassword_events" } lists exactly what to paste.

Will an AI agent use up my 1Password Events API API limit?

actionlake paces every call to the limits in the 1Password Events API service file: 600 calls a minute and 30,000 an hour per connection. Repeated reads are answered from cache (7 1Password Events API actions can be), which never reaches 1Password Events API.

What does a 1Password Events API action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (9 1Password Events API actions page). Cache hits, searches, dry runs and calls 1Password Events API refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which 1Password Events API API does it cover?

The Events API 1.4.1 (v1/v2) and 3.0.0 beta (v3 audit events) at events., under your region. It is built from 1Password Events API's documentation as read on 23 October 2026. 9 actions in 1 area, each one in the signed service file (version 1.0.0).

Does actionlake keep my 1Password Events API data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your 1Password Events API credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

Give your agent 1Password Events API today.

Connect 1Password Events API free See pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.

1Password Events API MCP server for AI agents.

Connect 1Password Events API in three steps.

Add actionlake to Claude.

Connect 1Password Events API.

Make the first call. Check before a write.