CallLint

Cline

CallLint support for Cline by Open Source. CallLint auto-discovers both Cline config files: the CLI's (~/.cline/data/settings/, relocatable via CLINE_DATA_DIR) and the VS Code extension's, which lives in per-extension globalStorage and is documented by no upstream page. Neither Cline's rules, hooks, skills, agents nor plugins directories are read, and ~/Documents/Cline/MCP/ holds installed server source rather than server registrations, so it is not a config path.

P2 Auto-detects

Why scan Cline?

Cline executes multi-step tasks from inside VS Code, so an MCP server it holds is callable across a whole task rather than for a single approved action.

Usage

CallLint can auto-discover and scan Cline configurations:

calllint scan --agent cline

How to start

Install nothing globally — run CallLint straight from npm:

npx calllint scan --auto

Then scan Cline specifically:

calllint scan --agent cline

How to verify it worked

Check which of the two config files the verdict header names. Cline's CLI and its VS Code extension keep separate server lists, so a clean scan of one says nothing about the other -- if you registered a server through the extension UI, the CLI file is the one that will look empty.

What CallLint does to Cline

Offline by default. Deterministic. Never executes the server it judges. SAFE means no blockers observed, not a proof of runtime safety.

A No blockers observed verdict means exactly that — no blocker under the evidence CallLint could collect. It is not a guarantee, and Insufficient evidence never becomes it on its own. See Coverage Boundary for what this scan does not look at.

Configuration Paths

CallLint looks for Cline configurations in:

  • ~/.cline/data/settings/cline_mcp_settings.json
  • $CLINE_DATA_DIR/settings/cline_mcp_settings.json
  • <appData>/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

Authority Surfaces

Cline can grant tools the following authority surfaces:

  • vscode-extensions
  • cli
  • tools
  • mcp

Distribution

CallLint is available for Cline through:

  • mcp-stdio (via officialMcpRegistry) — Available now
  • cline-marketplace-pr — Awaiting the upstream registry
    Existing PR #49 at cline/marketplace, do not create duplicate. Opened as a draft 2026-08-18 and marked ready for review 2026-08-26; it was ours to send, so it entered review only on the later date.

Support Status

Auto-detects — CallLint finds this host’s config on its own.

The commands under Usage are the ones CallLint actually supports for Cline today. Anything not listed there is not claimed.

Official Sources

Coverage Boundary

CallLint auto-discovers both Cline config files: the CLI's (~/.cline/data/settings/, relocatable via CLINE_DATA_DIR) and the VS Code extension's, which lives in per-extension globalStorage and is documented by no upstream page. Neither Cline's rules, hooks, skills, agents nor plugins directories are read, and ~/Documents/Cline/MCP/ holds installed server source rather than server registrations, so it is not a config path.