Updated
Devin Desktop / Cascade
This guide uses LyraShield's integration registry for the desktop 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
For Cascade in Devin Desktop, open the MCP config from the Cascade panel and add the LyraShield Streamable HTTP endpoint with OAuth. Add LyraShield skills under `.devin/skills`. This configuration does not apply to cloud Devin or the Devin Local agent.
Manual fallback: merge the following into ~/.config/devin/mcp_config.json. Complete OAuth in the client after adding the server. No API key belongs in this config.
{
"mcpServers": {
"lyrashield": {
"serverUrl": "https://app.lyrashieldai.com/api/mcp"
}
}
}Important gotchas
- This surface is Devin Desktop's legacy Cascade agent. The Devin Local agent uses separate CLI configuration; cloud Devin is configured in its web MCP Marketplace.
- Teams may disable MCP or restrict servers through allowlists. Cascade has no one-click MCP marketplace; Devin Local uses a separate marketplace.
- Cascade skills live in `.devin/skills`; Cascade hooks are separately configured and must remain opt-in.
Configuration locations
- global:
~/.config/devin/mcp_config.json
Native components and distribution
Documented client capabilities: skills, 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 devin-desktop --project --dry-runnpx -y lyrashield@0.2.14 skills install devin-desktop --projectRestart or reload the client and verify its skill list. Local files do not prove discovery, authentication, marketplace listing or runtime acceptance.
Distribution route: Direct MCP and skill setup; 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.