Updated 2026-08-07

Devin CLI

Devin CLI (by Cognition, separate from Devin's web application) reads MCP server configuration from .devin/config.local.json in your project root. This file is gitignored and uses a mcpServers object. Devin CLI supports stdio transport only.

Install with the CLI (fastest)

Run npx lyrashield install devin-cli from your project root. It detects Devin CLI, writes the correct config automatically, and never inlines your API key into a file you might commit. Add --dry-run first to preview the change with no write, or run npx lyrashield doctor afterward to confirm it's configured correctly.

npx lyrashield install devin-cli

Prefer to see exactly what gets written, or set it up without Node.js? Configure it by hand below.

Local stdio setup

Add the following to .devin/config.local.json. Create the file if it does not exist. You can also manage servers with devin mcp add.

Add the following to .devin/config.local.json. Recommended: run npx lyrashield login --oauth once; the local MCP server reads the selected workspace credential from ~/.lyrashield/credentials.json.

{
  "mcpServers": {
    "lyrashield": {
      "command": "npx",
      "args": [
        "-y",
        "@lyrashield/mcp"
      ],
      "env": {
        "LYRASHIELD_API_URL": "https://app.lyrashieldai.com"
      }
    }
  }
}

npx lyrashield install devin-cli

Important gotchas

• Devin CLI (separate from Devin Desktop) uses .devin/config.local.json (gitignored) with a mcpServers object; stdio only.
• Manage servers with `devin mcp add|login|enable|disable`; remote servers needing OAuth authenticate via `devin mcp login <server>`. MCP tools are namespaced mcp__<server>__<tool>.

Verify the connection

Run devin mcp list to confirm the lyrashield server is registered. Ask Devin: "What LyraShield tools do you have access to?" to confirm the server is connected.