Is this an official 1Password Events MCP server?

No. It is Memtro's MCP server with Memtro's 1Password Events connector behind it: the connector reads 1Password Events through its API with the credentials you connect on Dashboard → Connections, and 1Password Events publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in 1Password Events?

Not yet. Today every 1Password Events tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Engineering and operations

1Password Events MCP server

1Password Events in any MCP client, through Memtro: 1Password Events does not publish this server. Memtro's 1Password Events connector reads 1Password Events through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

1Password Business audit trail through the Events API: what team members did in the account (audit events), which items in shared vaults were revealed, copied, filled, edited or exported and by whom (item usages), and sign-in attempts with the reason any failed. People are named with their email; places are countries. IP addresses and finer locations are never returned. Read-only.

Reads

onepassword_token_infoWhich 1Password event feeds this connection's token may read (auditevents, itemusages, signinattempts), when it was issued, and the account's UUID.
onepassword_audit_events1Password audit events in a time window, oldest first: who (name, email and UUID) did what to which object (joined a group…
onepassword_item_usagesItems in shared 1Password vaults that were used in a time window, oldest first: the action (reveal, secure-copy, fill, enter-item-edit-mode, export…
onepassword_sign_in_attempts1Password sign-in attempts in a time window, oldest first: success or the kind of failure (credentials_failed, mfa_failed, sso_failed…

Connect it

First connect 1Password Events on Dashboard → Connections, then add Memtro to your client once. The 1Password Events tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared 1Password Events connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› Who exported items from shared vaults this week?
› Which sign-in attempts failed yesterday, and from which countries?
› Who changed vault permissions this month?
› Was anyone suspended in the last seven days?
› Which feeds can this token read?

Questions

Is this an official 1Password Events MCP server?: No. It is Memtro's MCP server with Memtro's 1Password Events connector behind it: the connector reads 1Password Events through its API with the credentials you connect on Dashboard → Connections, and 1Password Events publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in 1Password Events?: Not yet. Today every 1Password Events tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.