Other · Local MCP server

Logi Approval

Logi Agent Approval Gate - human approval on the phone before high-risk agent actions.

Visit Logi Approval's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
dev.1pass/logi-approval
Version
0.1.2
Status
Active
Category
other
Transport
stdio (local process)
Package
npm
Published
2026-08-07
Updated
2026-08-07
Publisher
dev.1pass · 2 servers with pages here
Namespace
Namespace verified by the MCP Registry via the domain 1pass.dev · how
Website
docs.1pass.dev/agent-approval/quickstart
Repository
github.com/dcode-co/logi-plugins
Source
Registry API entry

Packages

RegistryPackageVersionTransportEnvironment variables
npm@logi-auth/mcp-approval0.1.2stdioLOGI_AGENT_TOKEN (required, secret), LOGI_AGENT_PUBLIC_ID (required), LOGI_AGENT_PRIVATE_KEY (secret), LOGI_API_URL

How to connect Logi Approval

Logi Approval runs locally from a Node.js package published to the npm registry: @logi-auth/mcp-approval version 0.1.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @logi-auth/mcp-approval@0.1.2. It reads these environment variables: LOGI_AGENT_TOKEN (required, secret), LOGI_AGENT_PUBLIC_ID (required), LOGI_AGENT_PRIVATE_KEY (secret) and LOGI_API_URL; set them in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "logi-approval": {
      "command": "npx",
      "args": [
        "-y",
        "@logi-auth/mcp-approval@0.1.2"
      ],
      "env": {
        "LOGI_AGENT_TOKEN": "<secret>",
        "LOGI_AGENT_PUBLIC_ID": "<value>",
        "LOGI_AGENT_PRIVATE_KEY": "<secret>",
        "LOGI_API_URL": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More from dev.1pass

All 2 →
ServerRunsEndpoint or package
LogiLogi (1pass) IdP - manage your OAuth apps, redirect URIs, passkeys, login history and docs.Local · stdionpm: @1pass/mcp

More other servers

All 8,395 →
ServerRunsEndpoint or package
lockvetExplain any lockfile or workflow-pin change: bumps, vulns, ages, deprecations - 61 formats.Local · stdioOCI image (Docker): ghcr.io/matteo-sung/lockvet:0.6.20
LocusHierarchical markdown memory palace for AI agents - structured palace navigation via MCP tools.Local · stdioPyPI: locus-mcp
Lodestar StampDated, source-linked receipts before an agent recommends or books. Lodestar does not approve.Remote & Local · HTTP, stdioLive check: ✓ handshakeapi.lodestarindex.com
Logic ServerAgent reasoning, memory, and token-optimized context for AI applications.Local · stdionpm: nocturnusai-mcp
Logicnodes MCPRemote MCP for LogicNodes: Signed PII-Shield flagship + payable x402 agent tools on Base.Remote · HTTP, SSELive check: ✗ no handshakelogicnodes.io
Logicnodes MCP BridgeSigned PII-Shield: redact PII to an EIP-191 attestation, plus x402 pay-per-call agent tools.Local · stdionpm: @logicnodez/mcp-bridge
LogluneReproduce, inspect, diff and bisect feature-flag rulesets; author and publish flag changes.Remote · HTTPLive check: sign-in requiredloglune.com