Logi

dev.1passPublished by 1pass.devv0.2.2Updated Oct 24, 2026

logi (1pass) IdP — manage your OAuth apps, redirect URIs, passkeys, login history and docs.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A local MCP server for the logi (1pass) passkey-first sign-in service, letting an assistant manage OAuth apps, redirect URIs, passkeys, login history and docs.

What you can do
Manage OAuth apps and their redirect URIs for the logi identity provider, including registering relying parties for sign-in integration. Review passkeys and login history tied to the account. Look up logi documentation to guide OIDC and passkey integration work. The manifest lists no individual tools, so exact operations are not documented here.
When to use it
Useful when integrating 1pass/logi passkey or OIDC sign-in into an application and you want the assistant to inspect or adjust app settings and consult the docs. Also relevant for reviewing passkey and login history during setup or troubleshooting.
Requirements
Runs as a local process via the npm package @1pass/mcp over stdio, so Node.js and npx are needed. A Personal API key in LOGI_API_KEY is required for app and account tools; docs tools work without it. LOGI_API_URL optionally overrides the API base URL, which defaults to the logi service.
Before you install
LOGI_API_KEY is a personal credential granting access to your logi account; keep it out of shared configuration and logs. The server can change OAuth app settings and redirect URIs, which affects sign-in security, so review changes before applying them. Account data such as login history is sent to the logi API.

Installation

In SourceWeft

  1. Open Logi in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

logi (1pass) — Claude Code plugins

Agent plugins for logi / 1pass, the passkey-first sign-in service.

PluginWhat it does
logi-integrateIntegrate 1pass sign-in into your app — a skill that walks the agent through RP registration and OIDC integration, plus the @1pass/mcp server for managing your apps, redirect URIs, and docs lookup.
logi-approvalAgent Approval Gate — the agent asks a human for Face ID / passkey approval on their phone before performing a high-risk action. Bundles @logi-auth/mcp-approval.

Install (Claude Code)

bash
claude plugin marketplace add dcode-co/logi-pluginsclaude plugin install logi-integrate@logiclaude plugin install logi-approval@logi   # optional

Then set the env vars each server needs:

  • logi-integrate: LOGI_API_KEY — a Personal API Key from start.1pass.dev (Settings → API Keys).
  • logi-approval: LOGI_AGENT_TOKEN, LOGI_AGENT_PUBLIC_ID (and LOGI_AGENT_PRIVATE_KEY for signed mode) — see the Agent Approval quickstart.

Other agent clients (Cursor, Codex, Copilot, …)

The skills follow the open Agent Skills format — copy any plugins/*/skills/<name>/ directory into your client's skills directory. Add the MCP servers with your client's MCP configuration using the same npx commands found in each plugin's .mcp.json.

Single-file skill install without the plugin system:

bash
curl -fsSL https://docs.1pass.dev/skills/logi-rp-integrate/SKILL.md \  -o ~/.claude/skills/logi-rp-integrate/SKILL.md --create-dirs

Docs

License

MIT

Source: README.md at commit d14ba1d

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts