Skip to content

Updated

Auggie CLI

This guide uses LyraShield's integration registry for the cli surface. It shows the current setup strategy and client source; actual client loading and authenticated runtime acceptance are tracked separately below.

Connection setup

The registry's setup path for this client is Client configuration file over local stdio.

Client activation instructions

Auggie supports plugins through `/plugins` and `auggie plugin marketplace`, but LyraShield's Auggie marketplace artifact is still in preparation. This install entry writes the documented MCP server map to `~/.augment/settings.json`; use local stdio with the user's LyraShield credential for direct workflows. Auggie's current MCP docs describe static HTTP headers, not hosted OAuth.

Manual fallback: merge the following into ~/.augment/settings.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"
      }
    }
  }
}
Manual setup: the pinned CLI package (lyrashield@0.2.14) has no matching installer contract for this integration. Use the configuration or client instructions above and verify the client loads it.

Important gotchas

  • Auggie persists MCP servers in `~/.augment/settings.json`; the documented `auggie mcp add` command also manages this file. HTTP uses a `type: "http"` entry.
  • Auggie documents bearer headers for HTTP MCP but does not document OAuth for that transport. A hosted API key does not grant hosted mutation delegation; use stdio with a user-scoped credential for that authorization path.
  • Auggie plugins support skills, commands, rules, hooks and MCP, and also accept Claude Code plugin layouts. LyraShield's Auggie marketplace listing remains PREPARATION.
Hosted access: use OAuth when the client supports it. Hosted mutations require a browser-confirmed delegation and are checked against its workspace, scope and expiry. An API key alone does not authorize hosted mutations. See the Remote MCP guide.
Local access: run npx -y lyrashield@0.2.14 login --oauth to select a workspace for local stdio, or use a scoped workspace API key in an appropriate private environment. Never commit credentials.

Configuration locations

  • global: ~/.augment/settings.json

Native components and distribution

Documented client capabilities: plugin, skills, commands, rules, hooks. These describe what the client can load; use the installer and distribution details below to see which LyraShield components are available for this surface.

Distribution route: Auggie plugin marketplace; registry state PREPARATION. Client distribution documentation.

Support evidence

Registry tier: COMPATIBLE. Evidence: DOCUMENTATION, checked 2026-10-01. Client version: not recorded; tested platforms: not recorded. No client runtime receipt is recorded.Marketplace state and runtime compatibility are separate claims.

Source: Auggie CLI official documentation.