Skip to content
LyraShield AIOpen beta

Updated

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 CLI (fastest)

Run npx lyrashield install oh-my-pi from your project root. It detects Oh-My-Pi, writes the correct config automatically, and never inlines your API key into a file you might commit. Add --dry-run first to preview the change with no write, or run npx lyrashield doctor afterward to confirm it's configured correctly.

npx lyrashield install oh-my-pi

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.

Add the following to .omp/mcp.json. Recommended: run npx lyrashield login --oauth once; the local MCP server reads the selected workspace credential from ~/.lyrashield/credentials.json.

{
  "mcpServers": {
    "lyrashield": {
      "command": "npx",
      "args": [
        "-y",
        "@lyrashield/mcp"
      ],
      "env": {
        "LYRASHIELD_API_URL": "https://app.lyrashieldai.com"
      }
    }
  }
}
One-line install: the CLI writes exactly the configuration above.
npx lyrashield 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.

Add the following to .omp/mcp.json. Replace <LYRASHIELD_API_KEY> with your workspace API key.

{
  "mcpServers": {
    "lyrashield": {
      "url": "https://app.lyrashieldai.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <LYRASHIELD_API_KEY>"
      },
      "type": "http"
    }
  }
}
Read-only vs. read-and-write: Remote mutating tools (scan triggers, finding submissions, report creation) require an explicit OAuth write scope or write-capable API key, plus a human out-of-band approval. Read-only inspection tools work with any key.

Verify the connection

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

Requirements: Node.js 20+ and a LyraShield workspace API key. The@lyrashield/mcp package is published on npm, sonpx -y @lyrashield/mcp resolves directly.