Skip to content

Updated

OpenCode V2

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 Guided manual setup over remote HTTP.

Client activation instructions

For V2, add LyraShield with opencode mcp add lyrashield --url https://app.lyrashieldai.com/api/mcp and complete OAuth with opencode mcp auth lyrashield. If editing JSON manually, put the entry under mcp.servers.lyrashield; V2 uses type remote for HTTP and type local for stdio. The native skill locations remain .opencode/skills and ~/.config/opencode/skills.

Install type: No verified native MCP configuration is available for this client.
For V2, add LyraShield with opencode mcp add lyrashield --url https://app.lyrashieldai.com/api/mcp and complete OAuth with opencode mcp auth lyrashield. If editing JSON manually, put the entry under mcp.servers.lyrashield; V2 uses type remote for HTTP and type local for stdio. The native skill locations remain .opencode/skills and ~/.config/opencode/skills.
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

  • OpenCode V2 uses mcp.servers and a nested per-server object; the stable OpenCode entry represents V1 mcp root and is not interchangeable.
  • V2 MCP remote connections use OAuth by default and can be authorized through opencode mcp auth lyrashield; do not add a bearer header when using OAuth.
  • V2 skill discovery still uses .opencode/skills and ~/.config/opencode/skills and is compatible with the portable Agent Skills layout.
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: skills. 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 opencode-v2 --project --dry-run
npx -y lyrashield@0.2.14 skills install opencode-v2 --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: OpenCode V2 skills and MCP configuration; 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: OpenCode V2 official documentation.