Skip to content

Updated

Qwen Code

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 remote HTTP.

Client activation instructions

The documented `settings.json` MCP path supports hosted OAuth discovery and is ready for direct setup. LyraShield's Qwen extension package is still in preparation; once available, install it with `qwen extensions install` from its Git, archive or npm source, then inspect its tools and skills with `/mcp` and `/skills`.

Manual fallback: merge the following into .qwen/settings.json. Complete OAuth in the client after adding the server. No API key belongs in this config.

{
  "mcpServers": {
    "lyrashield": {
      "httpUrl": "https://app.lyrashieldai.com/api/mcp"
    }
  }
}
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

  • Qwen Code's documented HTTP setting is `httpUrl`; remote OAuth is discovered and handled by the client. Restart the client or use `/mcp` after adding a server.
  • Native Qwen extensions can bundle MCP servers, a context file, commands and skills. The extension loader uses `qwen-extension.json`; Agent Plugins v1 is a separate supported format and needs its own tested artifact.
  • For cloud-hosted Qwen sessions, configure a reachable OAuth redirect URI; the default localhost redirect works only when the user's browser can reach that session.
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: ~/.qwen/settings.json
  • project: .qwen/settings.json (shared by convention)

Native components and distribution

Documented client capabilities: plugin, skills, commands, rules. 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: Qwen Code extension via Git, archive or npm; 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: Qwen Code official documentation.