Skip to content

Updated

Junie IDE

This guide uses LyraShield's integration registry for the ide 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

For Junie in JetBrains IDEs, add the stdio server through Settings → Tools → Junie → MCP Settings, or edit .junie/mcp/mcp.json at project scope and ~/.junie/mcp/mcp.json at user scope. The IDE docs do not establish the remote OAuth flow available in Junie CLI, so use local stdio here. Add skills under .junie/skills or ~/.junie/skills.

Manual fallback: merge the following into .junie/mcp/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"
      }
    }
  }
}
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

  • Junie IDE MCP files use the mcpServers JSON object. Keep credentials out of shared project files and provide local environment values outside committed configuration.
  • Junie IDE and Junie CLI have separate entries because only the current CLI guide explicitly documents remote OAuth authorization.
  • Project settings and skills load only in a trusted project; inspect the IDE connection status and tool list after activation.
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

  • project: .junie/mcp/mcp.json (shared by convention)
  • global: ~/.junie/mcp/mcp.json

Native components and distribution

Documented client capabilities: skills, commands, rules, plugin, 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.

Install shared LyraShield skills

The pinned CLI includes a skills installer for this client. Preview its file changes first, then run the install command. Existing files that are not LyraShield-owned, or have been customized, are preserved.

npx -y lyrashield@0.2.14 skills install junie --project --dry-run
npx -y lyrashield@0.2.14 skills install junie --project

Restart or reload the client and verify its skill list. Local files do not prove discovery, authentication, marketplace listing or runtime acceptance.

Distribution route: Junie extensions and native skills; 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: Junie IDE official documentation.