VS Code

Install and initialize Signalint in the repository you want VS Code to check. The MCP entry point is signalint-mcp; the registry emits --no-install. Install the package and verify that the client can resolve it from its launch environment; that flag is not a project-root selector.

Source scope: The paths and command shapes below describe Signalint 1.2.1’s registry/emitter, not an integration test of every client version. Confirm the active configuration path and accepted keys in your client’s own settings/docs before copying. A registry marker only helps init select a candidate; it does not prove that an editor is installed or reading that file.

The v1 JSON merger requires strict JSON (not comments/trailing commas) and replaces the selected Signalint entry, including custom env or arguments. Back up and review settings before accepting a write. TOML setup replaces its Signalint block rather than providing a full configuration parser.

Project setup

Run npx signalint-mcp init to let Signalint detect the client and ask before updating its configuration. The v1 registry targets .vscode/mcp.json in the project root. Merge the example into the configuration your client actually uses, preserving unrelated servers.

macOS / Linux

{
  "servers": {
    "signalint": {
      "command": "npx",
      "args": [
        "--no-install",
        "signalint-mcp"
      ]
    }
  }
}

Windows

{
  "servers": {
    "signalint": {
      "command": "cmd",
      "args": [
        "/c",
        "npx",
        "--no-install",
        "signalint-mcp"
      ]
    }
  }
}

The Signalint registry does not emit cwd for this client. Confirm the inherited project root with ping after connecting. If the client starts the process elsewhere, use its environment settings to select SIGNALINT_PROJECT_ROOT for this workspace.

User setup

Signalint 1.2.1’s registry declares the workspace target, not a VS Code user-level path. For a user-level setup, follow your installed client’s own configuration editor/docs; this source audit does not infer an additional registry target.

Verify the connection

1. Restart or reconnect the client’s MCP server connection.
2. Call ping with {}. The text is pong; inspect structuredContent.projectRoot.
3. Confirm that the root is this repository, then call check_project with {}.

If the local package cannot be found, check the client’s working directory and Node PATH. For a fixed project, an absolute node entry-point path can bypass package-manager shims; see troubleshooting.

Continue with the quickstart, or read multiple projects before sharing one configuration across repositories.