How to Connect 1Password Events to Microsoft Copilot via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → 1Password Events, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

1Password Events + Microsoft Copilot

Activity feed of a 1Password Business account through the 1Password Events API: sign-in attempts with outcome, client and location, item usage events (fill, reveal, copy, export, share) and audit events for changes to users, vaults, groups and permissions. Read-only; it never returns passwords or other secret values.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

ONEPASSWORD_EVENTS_URL, ONEPASSWORD_EVENTS_TOKEN

Step 1 — Get credentials

Setting up takes about 5 minutes. You need a 1Password Business account and an owner or administrator who can set up an Events Reporting integration.

1. Sign in on 1Password.com and open Integrations (then Directory if other integrations already exist).
2. Under Events Reporting choose your SIEM, or Other, name the integration and select Add Integration.
3. Set up a bearer token: a name, an optional expiry (30, 90 or 180 days; without one it never expires) and the Events to Report: sign-in attempts, item usages, audit events. Select Issue Token and save the token in 1Password.
4. Paste the token (a long JWT starting with eyJ, without Bearer in front) into ONEPASSWORD_EVENTS_TOKEN.
5. Set ONEPASSWORD_EVENTS_URL to the events host of your account's region: https://events.1password.com (1password.com), https://events.ent.1password.com (ent.1password.com), https://events.1password.ca (1password.ca) or https://events.1password.eu (1password.eu).
6. Install the connector and run onepassword_events_introspect: it shows the token's uuid, when it was issued, the account and, in features, which event types it may read.

Read-only: the three list tools are POST requests only because the paging cursor travels in the request body; nothing in 1Password changes. There is nothing to write, so no tool is switched off at install.

No secret values: the events name users, vaults and items by uuid, with user names, emails, IP addresses and locations, but they never contain passwords or other item contents. To read vaults and items, use the separate 1Password Connect connector.

What it reads:

• onepassword_events_list_signin_attempts: successful and failed sign-ins with the user (name, email, uuid), time, outcome (category such as success, credentials_failed, mfa_failed, sso_failed, firewall_failed; type such as credentials_ok, mfa_ok, password_secret_bad, totp_bad, country_blocked), client app and version, OS, IP address and location. Useful for suspicious logins, failed MFA or blocked countries.
• onepassword_events_list_item_usages: who filled, revealed, copied, exported, shared or edited an item, or which integration fetched, created or updated it (fill, reveal, secure-copy, export, share, enter-item-edit-mode, select-sso-provider, server-fetch, server-create, server-update), with item_uuid, vault_uuid, used_version, user, client and location. Only 1Password apps 8.4.0 or later record item usage actions.
• onepassword_events_list_audit_events: what team members changed in the account, such as users invited, suspended or removed, vault access granted or revoked, groups, devices, service accounts and their tokens, and exports. Each event has action, object_type, the actor, the object, the session (IP, device, login time) and the location.

Each list tool needs the matching feature on the token (signinattempts, itemusages, auditevents); for a feature the token was not issued for, it answers 401.

Paging: the first call takes start_time, end_time (RFC 3339, for example 2026-10-29T00:00:00Z) and limit (1 to 1000, default 100); without times it returns the last hour. Every answer carries cursor and has_more. While has_more is true, the AI calls the same tool again with only cursor. A cursor stays valid across sessions, so it can be kept to fetch only newer events later. To change the window or the page size, the AI starts again without a cursor.

Data formats: items holds the events, oldest first. Times are RFC 3339 in UTC. Ids are 26-character uuids such as ETWZJTQCSRFPVOX74KERGHPBTU. country and location.country are ISO country codes. Audit action and object_type are short codes: grant, revoke, uva (user vault access), gva (group vault access), sa (service account), satoken (service account token).

Limits: 600 requests per minute and 30,000 per hour per token; a 429 means waiting until the window resets.

Common errors: 401 with {"Error":{"Message":"Unauthorized"}} means a wrong, revoked or expired token, the wrong regional host, or a feature the token was not issued for. 400 means a malformed time or limit. On 500, retry after a short wait and check https://status.1password.com.

The connector does not read vaults, items or passwords, does not change users, vaults or permissions, and does not issue or revoke Events Reporting tokens.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Microsoft Copilot

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.

1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
4. In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
5. Try it in the agent's Test pane: ask for something that needs the 1Password Events tools.
6. Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.

Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.

Available tools

Example prompts

• "Were there failed sign-in attempts to our 1Password account in the last 24 hours? Group them by user and country."
• "Which items were revealed or copied in the last 7 days, and by whom?"
• "List yesterday's audit events: who was invited, suspended or removed, and which vault permissions changed?"
• "Was a service account token created or revoked this month?"
• "Which event types can our Events Reporting token read?"

FAQ

Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.

What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.

The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse