Troubleshooting

Start with ping

After changing an MCP client configuration, restart or reconnect the client and call ping with {}. A working stdio connection returns pong. If initialization ends with EOF, run the server command in a plain terminal and confirm it waits on stdin without writing ordinary logs to stdout.

Windows command shims

Native Windows MCP clients commonly need cmd /c around npx. For Antigravity, use this shape:

{
  "mcpServers": {
    "signalint": {
      "command": "cmd",
      "args": ["/c", "npx", "--no-install", "signalint-mcp"],
      "cwd": "C:\absolute\path\to\project"
    }
  }
}

For an npm-link development build whose .cmd shim still fails, bypass the shim:

node C:\absolute\path\to\Signalint\dist\src\index.js
node C:\absolute\path\to\Signalint\dist\src\cli.js stats

TypeScript reports no issues unexpectedly

• Confirm there is a tsconfig.json at the project root.
• For a monorepo, use a solution-style root config with references pointing to composite projects.
• Run npx tsc --build manually for a solution-style config to compare raw compiler behavior.

check_files appears stale

The tsc invalidation decision sees only files explicitly supplied to that call. If file A changed but the call checks only unchanged file B that depends on A, the previous tsc result can be reused. Include every changed dependency file or run check_project.

An issue reference is stale

get_issue_detail references only the latest successful result. Run check_project again, then use a current clusterId or issueId.

Reset local state

Stop the MCP server before deleting .signalint/. The directory contains the SQLite cache, TypeScript incremental state, and session log. Deleting it while a server process is still running does not clear that process's in-memory loop state.

Inspect a check from the terminal

npx --no-install signalint check .

For persisted metrics, run npx --no-install signalint stats.