Updated 2026-10-02

Oh-My-Pi

Oh-My-Pi (omp.sh) reads MCP server configuration from .omp/mcp.json (project) or ~/.omp/agent/mcp.json (user). User config is profile-aware at ~/.omp/profiles/<profile>/agent/mcp.json. Oh-My-Pi also auto-discovers MCP servers from other tools like Claude Code and Cursor, so if you already have LyraShield configured for those agents, Oh-My-Pi may pick it up automatically.

Install with the pinned CLI

CLI 0.2.14 has a matching installer for this client. Sign in first with npx -y lyrashield@0.2.14 login --oauth for local stdio. Review the planned changes before writing:

npx -y lyrashield@0.2.14 install oh-my-pi --dry-run

When the preview is correct, run the installer:

npx -y lyrashield@0.2.14 install oh-my-pi

The installer updates LyraShield's entry and preserves unrelated configuration. You can also use the manual snippet below. Restart or reload the client and complete a read-only authenticated call; an installed config entry alone does not prove client discovery.

Prefer to see exactly what gets written or set it up without Node.js? Configure it by hand below.

Local stdio setup

Add the following to .omp/mcp.json or ~/.omp/agent/mcp.json. The stdio type may be omitted (default stdio {command, args, env}). You can also use omp mcp add or omp plugin to manage servers.

Manual fallback: merge the following into .omp/mcp.json. Recommended: run npx -y lyrashield@0.2.14 login --oauth once; the local MCP server reads the selected workspace credential from ~/.lyrashield/credentials.json. If you use an API key instead, set it in your private process environment before starting the client.

{
  "mcpServers": {
    "lyrashield": {
      "command": "npx",
      "args": [
        "-y",
        "@lyrashield/mcp@0.2.12"
      ],
      "env": {
        "LYRASHIELD_API_URL": "https://app.lyrashieldai.com"
      }
    }
  }
}

npx -y lyrashield@0.2.14 install oh-my-pi

Important gotchas

• Project config is `.omp/mcp.json`; user config is `~/.omp/agent/mcp.json` (profile-aware at `~/.omp/profiles/<profile>/agent/mcp.json`). Oh-My-Pi also auto-discovers MCP servers from other tools like Claude Code and Cursor.
• Remote uses `type: "http"` for Streamable HTTP; stdio `type` may be omitted (default stdio `{command, args, env}`). Supports OAuth via `auth`/`oauth` fields, plus `/mcp add` and `omp plugin`.

Remote HTTP setup

For environments where you prefer not to run a local process, connect to the remote endpoint. Oh-My-Pi uses type: "http" for Streamable HTTP. Supports OAuth via auth/oauth fields.

Manual fallback: merge the following into .omp/mcp.json. Enter the workspace API key only in the client's private, untracked server settings or its documented secret-backed header interpolation. The snippet contains a placeholder; never put a real key in a shared project file or shell command.

{
  "mcpServers": {
    "lyrashield": {
      "url": "https://app.lyrashieldai.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <LYRASHIELD_API_KEY>"
      },
      "type": "http"
    }
  }
}

Verify the connection

Restart Oh-My-Pi and ask: "What LyraShield tools do you have access to?" to confirm the server is connected.