Skip to content

Updated

Continue

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

Create a Continue MCP block at .continue/mcpServers/lyrashield.yaml with required name, version and schema v1 metadata. Add a stdio server with command npx and args -y plus @lyrashield/mcp@0.2.12, and environment values for the LyraShield API URL and a user-provided LYRASHIELD_API_KEY. Keep secrets in Continue local secrets or environment support; its current MCP guide does not document remote OAuth. Project rules can be placed under .continue/rules.

Install type: No verified native MCP configuration is available for this client.
Create a Continue MCP block at .continue/mcpServers/lyrashield.yaml with required name, version and schema v1 metadata. Add a stdio server with command npx and args -y plus @lyrashield/mcp@0.2.12, and environment values for the LyraShield API URL and a user-provided LYRASHIELD_API_KEY. Keep secrets in Continue local secrets or environment support; its current MCP guide does not document remote OAuth. Project rules can be placed under .continue/rules.
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

  • Continue's project MCP blocks are YAML files under `.continue/mcpServers/`; the required wrapper fields are `name`, `version` and `schema: v1`, with MCP servers represented as a list.
  • Continue documents Streamable HTTP but its MCP guide does not document OAuth. This registry entry uses local stdio; do not put a hosted API key in a shared project file.
  • Rules are separate files under `.continue/rules`. This entry covers the IDE configuration contract; the Continue CLI surface requires separate acceptance.
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: 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: Continue Hub and project-local MCP/rules blocks; registry state DIRECT. 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: Continue official documentation.