Updated 2026-10-02

Cline

Cline CLI reads MCP servers from ~/.cline/data/settings/cline_mcp_settings.json. Cline IDE extensions expose their own MCP settings JSON through the MCP Servers panel.

Install with the pinned CLI

CLI 0.2.14 has a matching installer for this client. Sign in first with npx -y lyrashield@0.2.14 login --oauth for local stdio. Review the planned changes before writing:

npx -y lyrashield@0.2.14 install cline --global --dry-run

When the preview is correct, run the installer:

npx -y lyrashield@0.2.14 install cline --global

The installer updates LyraShield's entry and preserves unrelated configuration. You can also use the manual snippet below. Restart or reload the client and complete a read-only authenticated call; an installed config entry alone does not prove client discovery.

Local stdio setup

Manual fallback: merge the following into ~/.cline/data/settings/cline_mcp_settings.json. Recommended: run npx -y lyrashield@0.2.14 login --oauth once; the local MCP server reads the selected workspace credential from ~/.lyrashield/credentials.json. If you use an API key instead, set it in your private process environment before starting the client.

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

npx -y lyrashield@0.2.14 install cline

Important gotchas

• Cline CLI reads `~/.cline/data/settings/cline_mcp_settings.json` (override with `CLINE_MCP_SETTINGS_PATH`); IDE extensions expose their own MCP settings JSON through the Cline panel.
• Cline defaults to legacy SSE when `type` is omitted; the remote endpoint needs `type: "streamableHttp"` explicitly.

Remote Streamable-HTTP setup

For environments where you prefer not to run a local process, connect to the remote endpoint.

Manual fallback: merge the following into ~/.cline/data/settings/cline_mcp_settings.json. Enter the workspace API key only in the client's private, untracked server settings or its documented secret-backed header interpolation. The snippet contains a placeholder; never put a real key in a shared project file or shell command.

{
  "mcpServers": {
    "lyrashield": {
      "url": "https://app.lyrashieldai.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <LYRASHIELD_API_KEY>"
      },
      "type": "streamableHttp"
    }
  }
}

Verify the connection

Open the Cline panel in VS Code and check the MCP server status. Ask Cline: "What LyraShield tools are available?" to confirm the server is connected.