Skip to content

Updated

Kiro Power and MCP setup

Kiro's native Power path is the intended LyraShield integration. Kiro supports Powers in its IDE and web surfaces, and the CLI supports them from v3. LyraShield's Power distribution is still in preparation, so there is no public Power package to install yet. The local MCP fallback below uses the published LyraShield MCP package and can be set up now.

Native path: Kiro Power

When LyraShield's Power is published, install it through Kiro's Power panel or the official Power page. A Power owns activation of its bundled MCP server and native components. Until then, treat the LyraShield Power as preparation only: it is not publicly installable and has no Kiro-authenticated runtime receipt.

Kiro Power installation documentation· Kiro Powers· Kiro MCP configuration

Current fallback: local MCP in Kiro IDE or CLI

For a Kiro surface with local MCP settings, log in and merge this entry into the workspace file .kiro/settings/mcp.json or the user file ~/.kiro/settings/mcp.json. The command uses the currently published MCP package.

npx --yes lyrashield@0.2.14 login --oauth
{
  "mcpServers": {
    "lyrashield": {
      "command": "npx",
      "args": ["-y", "@lyrashield/mcp@0.2.12"]
    }
  }
}

Merge only the lyrashield entry so existing servers stay intact. Credentials remain in the local LyraShield credential store and do not belong in Kiro's settings file.

No credential in committed files: After npx --yes lyrashield@0.2.14 login --oauth, the local MCP server reads credentials from ~/.lyrashield/credentials.json (or the LYRASHIELD_API_KEY environment variable). Nothing with a key needs to be committed.

Hosted MCP option

Where your Kiro surface supports remote MCP and browser OAuth, you can connect to LyraShield's hosted endpoint without the local MCP process. This setup path is documented but does not yet have a retained Kiro-authenticated runtime receipt. Do not create a duplicate connection if a working LyraShield entry is already present.

{
  "mcpServers": {
    "lyrashield": { "url": "https://app.lyrashieldai.com/api/mcp" }
  }
}

Verify the connection

Restart Kiro or reconnect MCP servers, then run a read-only LyraShield workspace query. An installed entry does not establish that the client loaded the tools or completed an authenticated call.

Local MCP requirement: Node.js 24+ and a LyraShield workspace OAuth login. Kiro launches the published local MCP package over stdio; the package reads the user-only credential store. Kiro CLI Powers require v3 or later.