Skip to content

Updated

Qoder 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 Guided manual setup over local stdio.

Client activation instructions

In Qoder IDE, open Extensions → Connectors to add LyraShield as a custom MCP server, or use Extensions → Plugins/Skills to import a local package once the LyraShield artifact is prepared. Qoder IDE documentation does not establish a stable MCP or standalone skill file path, so configure it through the UI.

Install type: No verified native MCP configuration is available for this client.
In Qoder IDE, open Extensions → Connectors to add LyraShield as a custom MCP server, or use Extensions → Plugins/Skills to import a local package once the LyraShield artifact is prepared. Qoder IDE documentation does not establish a stable MCP or standalone skill file path, so configure it through the UI.
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

  • Qoder IDE MCP and skill import use Extensions UI; the CLI's `.qoder/settings.json` and `.qoder/skills` paths belong to the separate Qoder CLI surface.
  • Qoder IDE supports imported plugins bundling skills, MCP, commands, rules and hooks. LyraShield's client package is still in preparation.
  • Review MCP permissions and connector authentication in the UI before use; this IDE entry does not inherit Qoder CLI's OAuth flow or configuration paths.
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.

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: Qoder IDE Plugins and 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: Qoder IDE official documentation.