Vibe Hnindex MCP Server

What the code does

We read the source, 22 h ago · rules 3dff92dd89df

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

  const result = spawnSync(cmd, ['update', '-g', 'hnindex-cli'], {

      : path.join(project.rootPath, edit.file_path);

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add vibe-hnindex -- npx -y vibe-hnindex

{
  "mcpServers": {
    "vibe-hnindex": {
      "args": [
        "-y",
        "vibe-hnindex"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.vibe-hnindex]
command = "npx"
args = ["-y", "vibe-hnindex"]

{
  "mcpServers": {
    "vibe-hnindex": {
      "args": [
        "-y",
        "vibe-hnindex"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "vibe-hnindex": {
      "args": [
        "-y",
        "vibe-hnindex"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: OLLAMA_URL (Ollama embedding server URL), OLLAMA_MODEL (Ollama embedding model name (default: bge-m3:567m)), QDRANT_URL (Qdrant vector database URL), STORAGE_PATH (SQLite database storage path). The author declared them in the registry entry; get the values from the project itself.