Skip to content

Updated

Amp

Amp uses a CLI command to register MCP servers. It can also load MCP configuration from an Agent Skill, which keeps the tools out of context until that skill is needed.

Keep secrets out of config: Local stdio can use a LyraShield CLI OAuth login. For an API-key fallback, export it in the shell rather than hardcoding it in a command or settings file.

Install with the CLI (fastest)

Run npx lyrashield install amp. It shells out to amp mcp add on your behalf with the correct command and arguments filled in — the same result as the manual step below, without retyping it. Use lyrashield login --oauth for the local credential store or export LYRASHIELD_API_KEY for an API-key fallback.

npx lyrashield install amp

Register via CLI

Run the following command in your terminal. Export LYRASHIELD_API_KEY in your shell profile (~/.bashrc, ~/.zshrc, etc.) so it is available when Amp starts the server.

Install type: Amp: run the command below to add the local server. Use the pinned LyraShield CLI OAuth login or store an API key in the private environment that launches Amp.

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.

LYRASHIELD_API_URL=https://app.lyrashieldai.com amp mcp add lyrashield -- npx -y @lyrashield/mcp@0.2.12
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

  • Amp takes no --env flags for its local stdio CLI; use a local OAuth credential or export a key. Remote HTTP/OAuth is a separate client-managed definition.
  • Amp can use global or workspace settings. The CLI command adds an always-available server; use an Agent Skill when the tools should only load for a relevant task.

Remote OAuth alternative

Current Amp also supports client-managed remote MCP definitions and OAuth. Use the command below as a separate connection, then verify tool discovery and a read call before replacing stdio.

amp mcp remote --personal add LyraShield https://app.lyrashieldai.com/api/mcp --auth oauth

Verify the connection

List registered servers with amp mcp list. The lyrashield server should appear. Start Amp and ask: "What LyraShield tools are available?" to confirm tools surface correctly.

Requirements: For local stdio, Node.js 24+ and a local OAuth login or workspace API key. Remote OAuth needs no local key. The @lyrashield/mcp package is published on npm, so npx -y @lyrashield/mcp@0.2.12 resolves directly.