@logi/mcp — Drive logi from Claude/Cursor

Manage logi in natural language from AI tools that support MCP, such as Claude Code, Claude Desktop, and Cursor.

For example: "Show me all of my logi apps that aren't on the production tier," or "Send alice@example.com an invite with admin permissions."

Two usage modes

Mode	Who	What
End-user mode	Regular users	Manage your own sign-in activity, passkeys, and connected apps
Developer mode	OAuth app developers	OAuth app CRUD, secret rotation, team management

The set of tools you see depends on the scope of the PAK (Personal API Key) you issue.

Installation

Pre-release

This has not been published to npm yet.

~/.claude.json (Claude Code):

{
  "mcpServers": {
    "logi": {
      "command": "node",
      "args": ["/Users/you/toy/logi/mcp/dist/index.js"],
      "env": {
        "LOGI_API_URL": "https://api.1pass.dev",
        "LOGI_API_KEY": "lpa_pat_xxxxxxxxxxxxx"
      }
    }
  }
}

After publish:

{
  "command": "npx",
  "args": ["-y", "@logi/mcp"]
}

Issue a PAK from start.1pass.dev → API Keys or /api/v1/me/api_keys. For end-user mode, select scopes such as login_history:read; for developer mode, select apps:manage and apps:read.

End-user mode tools (8)

Tool	Description	Required scope
logi_whoami	Check connection status + account	—
logi_list_login_history	Recent sign-in activity	login_history:read
logi_delete_login_log	Soft-delete a specific log	login_history:write
logi_list_trashed_logs	View the trash	login_history:write
logi_restore_login_log	Restore	login_history:write
logi_list_passkeys	List passkeys	passkeys:read
logi_delete_passkey	Delete a passkey	passkeys:manage
logi_list_connected_apps	View connected apps + permissions	apps:read

Docs tools (3, no auth required)

These work even without API key configuration. They fetch the public markdown mirror at docs.1pass.dev/llms/* — designed so the agent references the correct docs on its first attempt when integrating logi (the LangChain mcpdoc pattern).

Tool	Description	Required scope
logi_fetch_quickstart	The agent quickstart guide (lang=ko|en)	—
logi_get_doc	Fetch a specific doc path (allowed prefixes: guide/, oauth/, cli/, and so on)	—
logi_list_docs	The llms.txt sitemap — a list of available doc paths	—

> How do I integrate logi? (→ logi_fetch_quickstart)
> Tell me about the OAuth scope types (→ logi_get_doc path=oauth/scopes.md)
> What logi docs are there? (→ logi_list_docs)

Examples

> Show me my last 10 logi sign-in events
> Were there any suspicious logins yesterday? Filter to outside Korea only.
> Clean up the passkeys I no longer use
> I want to disconnect Notion

Developer mode tools (coming soon)

OAuth app developers managing apps in natural language from Claude/Cursor:

Tool	Description	Required scope
logi_apps_list	List apps in my org	apps:read
logi_apps_create	Register a new app	apps:manage
logi_apps_show	App details	apps:read
logi_apps_edit	Edit metadata and redirect URIs	apps:manage
logi_apps_rotate_secret	Rotate client_secret	apps:manage
logi_apps_delete	Delete an app	apps:manage
logi_team_invite	Invite a member	org:manage
logi_audit_logs	View audit logs	org:read

Developer examples

> Rotate the client_secret for "Demo Test App" and write the new value into .env
> Invite alice@example.com to our org as an admin
> Who changed a redirect URI last week?
> Create a new app for the staging environment with redirect_uri https://staging.acme.com/cb

Flow

Claude calls a tool → returns the result → suggests the next action. For example, after rotating a secret, it automatically offers to update your .env file.

Security

• Every call uses PAK authentication (injected only via env, never exposed in memory or logs)
• Sensitive operations (deletion, secret rotation) will gain iOS app step-up push approval in the future
• The MCP server prints only the first 8 characters of the PAK prefix to stdout/stderr, masking the rest

Next

• PAK issuance + scope model
• Audit logs — who did what
• The CLI is supported too