MCP.Market

Logi MCP server

by 1pass.dev·dev.1pass/logi·v0.2.2

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

B75/100grade B
What users say
No reviews yet
Be the first
Safety scan
B75/100

full report

Adoption
New

0 stars29 downloads/wk

Reviews

Write one

Nobody has reviewed Logi yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Logi tools (15, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • logi_add_redirect_uri

    Use when the user (RP owner) wants to register a new OAuth callback URL — for example after deploying to a new domain (easybracket.org), adding an iOS scheme, or staging environment. Idempotent: no-op if the URI is already registered. Server-side validators run (URI shape, sandbox host whitelist, app_link host match) and the change is recorded in developer_audit_logs. Requires PAK scope apps:manag

  • logi_delete_login_logwrite action

    Use when the user wants to remove a specific login record from view (e.g. 'delete that suspicious entry'). Soft-delete only — recoverable for 90 days. Requires the row `id` from logi_list_login_history. Do NOT use this to revoke a session or block future logins; that's a different scope.

  • logi_delete_passkeywrite action

    Use when the user explicitly asks to remove a specific passkey (e.g. lost device, old laptop). Destructive and irreversible — confirm with the user before calling. Takes the passkey `id` from logi_list_passkeys.

  • logi_fetch_quickstart

    Use when the user (or an agent) needs the logi/1pass agent quickstart guide — typical triggers: 'logi 어떻게 통합해?', 'how do I integrate 1pass?', 'logi 시작 가이드', or before generating RP integration code. Read-only, no auth required (fetches public docs.1pass.dev/llms/guide/agent-quickstart.md). Default lang=ko; pass lang=en for English. Prefer this over web search for logi onboarding docs.

  • logi_get_doc

    Use when the user asks about a specific logi/1pass topic (OAuth scopes, PKCE, redirect URI rules, CLI commands, security model, panopticon, agent approval, etc.) and you need the canonical doc text. Read-only, no auth required (fetches public docs.1pass.dev/llms/{path}). Path must be like 'oauth/scopes.md', 'guide/security.md', 'cli/overview.md'. Allowed prefixes: guide/, oauth/, integrations/, tr

  • logi_list_apps

    Use when the user (as a developer) asks 'what OAuth apps do I own?', 'list my RPs', or needs the app id before adding/removing a redirect_uri. Read-only. Returns id, name, client_id, status, and current redirect_uris for every app the PAK owner can manage. Requires PAK scope apps:read or apps:manage. Do NOT use to list end-user authorized apps — that's logi_list_connected_apps.

  • logi_list_connected_apps

    Use when the user asks 'which apps can see my data?', 'what have I authorized?', or wants to revoke third-party access. Read-only. Returns OAuth applications with active consent + the specific claims (email, phone, etc.) shared with each. Pair with the developer portal to revoke individual grants.

  • logi_list_docs

    Use when you (or the user) need to discover what logi/1pass docs exist — typically as a first step before logi_get_doc, or when the user asks 'what docs are available?'. Read-only, no auth required (fetches public docs.1pass.dev/llms.txt sitemap). Returns the canonical list of doc paths with brief titles.

  • logi_list_login_history

    Use when the user asks about recent sign-ins, suspicious access, login locations, or wants to audit account activity. Read-only. Returns the latest N (default 30, max 100) login events with country, IP, and a suspicious flag. Each row carries an `id` you can pass to logi_delete_login_log.

  • logi_list_passkeys

    Use when the user wants to see their registered Passkeys (Face ID / Touch ID / hardware key) — typically before deleting a stale one or auditing devices. Read-only. Returns name, created_at, last_used_at per passkey.

  • logi_list_trashed_logs

    Use when the user asks 'what did I delete?' or wants to review/restore previously soft-deleted login records. Read-only. Returns rows still within the 90-day grace window. Pair with logi_restore_login_log to undo.

  • logi_remove_redirect_uriwrite action

    Use when the user (RP owner) wants to deregister an old/unused OAuth callback URL — for example a historical onrender.com host that's been migrated to a custom domain. Refuses to remove the last remaining URI (would disable OAuth entirely). Server-side validators + audit log apply. Requires PAK scope apps:manage. Confirm with the user before calling.

  • logi_restore_login_log

    Use when the user wants to undo a deletion ('restore that log', 'I deleted the wrong one'). Takes an `id` from logi_list_trashed_logs. Idempotent — restoring an already-restored row is a no-op.

  • logi_show_app

    Use when the user wants the full RP record for one app (all fields: redirect_uris, app_link_url, allowed_scopes, client_type, webhook_url, status, etc.). Read-only. Takes the `id` from logi_list_apps. Requires PAK scope apps:read or apps:manage.

  • logi_whoami

    Use when the user asks 'am I logged in?', 'which logi account is this?', or whenever you need to verify the configured PAK is valid before another tool call. Read-only. Returns the email + scopes of the current PAK. Do NOT use to list login history — use logi_list_login_history.

Public scan report

scanner v0.1.9 · 2026-09-23 · same rubric, same numbers if you re-run it

no findings
  • Code scan7 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 47 days ago12/15
  • Maintainer identitynamespace and repository owner differ; website matches verified namespace6/10
Overall 75/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Logi compares

Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
75/100
higher than 40% of 1,299 Productivity servers
Tools
15
the typical Productivity server has 7
Tools that change things
20%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
29
more than 13% of 427 Productivity servers with a package

What its tools let an agent do: 12 read · 3 change

Install Logi in Claude Code, Cursor or VS Code

Runs npx -y @1pass/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add logi -- npx -y @1pass/mcp
Add to Cursor

What the publisher says

From the Logi repository's README, as published. We do not edit it. Read it on GitHub

logi (1pass) — Claude Code plugins

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

Install (Claude Code)

claude plugin marketplace add dcode-co/logi-plugins
claude plugin install logi-integrate@logi
claude plugin install logi-approval@logi   # optional

Then set the env vars each server needs:

start.1pass.dev (Settings → API Keys).

  • logi-integrate: LOGIAPIKEY — a Personal API Key from

(and LOGIAGENTPRIVATE_KEY for signed mode) — see the Agent Approval quickstart.

  • logi-approval: LOGIAGENTTOKEN, LOGIAGENTPUBLIC_ID

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

The skills follow the open Agent Skills format — copy any plugins/*/skills// 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:

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

Docs

  • Integration guides: https://docs.1pass.dev
  • LLM-readable docs: https://docs.1pass.dev/llms.txt

License

MIT

Nothing above is checked by us. What we check is on the safety report.

Logi: common questions

Is Logi MCP server safe?
Mostly: it is graded B (75/100). Read the Logi safety report
How do I install Logi?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Logi need an API key?
Yes. The registry entry asks for LOGI_API_KEY.
Is Logi maintained?
The last commit was 89 days ago (2026-08-07). The latest release is v0.2.2.
What can I use instead of Logi?
Servers from other publishers that do the same job: Orbit MCP server, Workfile MCP server and Context7 MCP server.
How does Logi compare with other Productivity MCP servers?
safety score 75/100 (higher than 40% of 1,299 Productivity servers); tools 15 (the typical Productivity server has 7); tools that change things 20% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Logi

Same job from other publishers: the closest match first, then the best rated.

  • Orbit
    Task management for people and AI agents, with scoped OAuth access to issues, projects, and docs.
    A
  • Workfile
    Repository-native protocol and local MCP server for Work, Docs, History and durable project Memory.
    A
  • Context7
    Up-to-date docs for AI agents
    A
  • Argent
    Drive iOS Simulators, Android emulators, TVs and Electron/web apps from your coding agent
    A
  • Svelte MCP
    The official Svelte MCP server providing docs and autofixing tools for Svelte development
    A