1Password MCP server for AI agents

Live

BEARER TOKEN

SECURITY EVENTS

Monitoring

1Password gives your agent read access to your account's security events: sign-in attempts, item usage in shared vaults, and audit events for account and vault changes, from the 1Password Events Reporting feeds.

  • Per-user credentials: each call uses the actual user's access token, never a shared bot.
  • Encrypted per-tenant vault: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: pre-call scope check, 90-day SIEM-exportable audit chain.
1Password
agent · Acme Q3
Run
Were there any failed sign-ins to 1Password this week?
S
onepassword_list_sign_in_attempts
121ms
Security agent
12 sign-ins failed this week. 9 were MFA failures for jordan@acme.com, all from one IP address in Lisbon.
Sources: 214 sign-in attempts
onepassword
214 attempts
18:29
Message Claude...

Tools your security agent reaches for on 1Password, scoped per user.

CALL ANY TOOL
4 read-only tools for security events in 1Password: check token features and list sign-in attempts, item usages, and audit events.
onepassword_get_token_info
Get token info
Inspect the connected 1Password Events Reporting token. Returns the token uuid, issued_at timestamp, the account_uuid it belongs to, and its features list (any of signinattempts, itemusages, auditevents). Use it to check which event feeds this connection can read before calling onepassword_list_sign_in_attempts, onepassword_list_item_usages, or onepassword_list_audit_events.
Parameters
Name
Type
Required
Description
—
No parameters required
onepassword_list_audit_events
List audit events
onepassword_list_item_usages
List item usages
onepassword_list_sign_in_attempts
List sign in attempts
Build your Agent
Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// 1Password tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["onepassword"], toolNames: [
    "onepassword_get_token_info",
    "onepassword_list_sign_in_attempts",
    "onepassword_list_audit_events"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Report failed sign-ins and vault access changes from the last 7 days" }] });
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["onepassword"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Report failed sign-ins and vault access changes from the last 7 days" }],
  tools,
});

// Execute the tool call with the user's vaulted 1Password access token
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["onepassword"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Report failed sign-ins and vault access changes from the last 7 days" }],
  tools,
});

// Tool call runs with the user's vaulted 1Password access token
await sk.tools.executeTool(msg.content, "user_123");
import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["onepassword"] }, pageSize: 100,
});

const agent = new Agent({
  name: "security_agent",
  model: "gemini-2.5-pro",
  instruction: "1Password tools scoped to this user",
  tools,
});

await agent.run("Report failed sign-ins and vault access changes from the last 7 days");
Try these prompts
Copy any prompt into your agent. Each maps directly to a 1Password tool. Click to copy, paste into your agent, done.
Sign-ins
Copy the prompt
Copied
List failed 1Password sign-ins from the last 7 days.
Copy the prompt
Copied
Which sign-ins failed on MFA this week?
Copy the prompt
Copied
Show sign-in attempts from outside the US today.
Item usage
Copy the prompt
Copied
Who revealed items in the Production vault this week?
Copy the prompt
Copied
List every export of a shared item this month.
Copy the prompt
Copied
Show usage of the AWS root item since Monday.
Audit events
Copy the prompt
Copied
Which vaults were created or deleted this month?
Copy the prompt
Copied
Who granted vault access in the last 24 hours?
Copy the prompt
Copied
Which event feeds can this connection read?
SEE HOW AUTH WORKS
Each user connects their own 1Password access token once, and Scalekit sends it with every call. Tokens stay vaulted, every call is scope checked, and every action is logged.
1
Authorize
Your user connects
1Password
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
1Password
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
1Password
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
1Password
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other monitoring connectors.
Engineering Teams
DevOps assistant agent
Polls GitHub for failing checks and stale PRs, opens Linear issues for the ones that need work, and posts a daily digest to Slack. It acts as the engineer, not a shared service account.
Test other agents
See the same per-user auth pattern across other monitoring connectors.
ENGINEERING
DevOps assistant agent
Poll GitHub for failing checks and stale pull requests, open Linear issues for the ones that need work, and digest to Slack.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Shared tokens break per-user analytics
A shared 1Password access token looks fine in a demo. In production every security event query looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.
// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
1Password today. Ten connectors tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access 1Password as the user or through a shared token?
As the user. Each user connects their own 1Password access token once, and Scalekit sends it with every call. The token is a 1Password Events Reporting token, so the agent reads sign-in, item usage, and audit event feeds and never reads or changes vault items.
Where is the 1Password access token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new access token. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.
Can I limit what the agent does in 1Password?
Yes. Filter by tool name in listScopedTools to expose only what you want, for example onepassword_list_sign_in_attempts without onepassword_list_item_usages. Every 1Password tool is read-only, so the agent cannot change the account, vaults, or items. Scalekit also enforces scope checks before every API call.
What happens when a user revokes 1Password access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.
Which 1Password events can the agent read?
The feeds the token includes: signinattempts, itemusages, and auditevents. onepassword_get_token_info returns the token's features and the account it belongs to, so the agent can check which feeds are available before it calls the list tools.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""onepassword"": {
""url"": ""https://mcp.scalekit.com/onepassword"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.onepassword]
url = ""https://mcp.scalekit.com/onepassword""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""onepassword"": {
""url"": ""https://mcp.scalekit.com/onepassword"",
""type"": ""http""
}
}
}