Zed

Install and initialize Signalint in the repository you want to check. Signalint 1.2.1’s registry targets the user-scoped ~/.config/zed/settings.json file. This describes its emitter, not proof that every Zed version/platform uses that location or accepts the same schema.

Zed settings can contain JSONC. The v1 automatic merger uses strict JSON.parse and can fail on comments or trailing commas; use the client’s settings editor and preserve existing configuration. Back up before replacing the Signalint entry.

Configure the context server

Merge the entry under context_servers, preserving any existing servers:

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

Signalint emits the nested command.path and command.args shape for Zed. Do not replace it with another client’s mcpServers shape.

For a Windows client using npm shims, the corresponding command is:

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

The settings location can vary with your platform and Zed version; use Zed’s settings editor when the registry path is not the active one.

Verify the workspace

1. Restart or reconnect the context server.
2. Call ping with {} and inspect structuredContent.projectRoot.
3. Confirm the root is the open repository before calling check_project.

This is a shared user entry without a project cwd. The process must inherit the correct workspace root. If it does not, use a deliberate project-root environment override in your launcher rather than assuming it follows the active editor automatically.

If --no-install cannot find Signalint, verify the working directory and Node PATH. See troubleshooting for an absolute Node entry-point fallback.

Continue with the quickstart and multiple-projects guide.