Windsurf

Install and initialize Signalint in the repository you want Windsurf 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.

User setup

The Signalint registry supports Windsurf through the user configuration at ~/.codeium/windsurf/mcp_config.json. Open the client’s MCP settings or merge this entry manually:

macOS / Linux

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

Windows

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

Do not add a hardcoded repository cwd to this shared entry. The process must inherit the workspace root, or use an explicit environment override deliberately for the active project.

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.