Hemnet MCP Server

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 hemnet-mcp -- npx -y hemnet-mcp

{
  "mcpServers": {
    "hemnet-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "hemnet-mcp"
      ]
    }
  }
}

[mcp_servers.hemnet-mcp]
command = "npx"
args = ["-y", "hemnet-mcp"]

{
  "mcpServers": {
    "hemnet-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "hemnet-mcp"
      ]
    }
  }
}

{
  "servers": {
    "hemnet-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "hemnet-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: HEMNET_TRANSPORT (Transport mode: `auto` (default) tries a direct anonymous fetch and switches to the ContextMint Bridge browser bridge when Hemnet serves a Cloudflare challenge; `direct` fails hard when walled; `fetchproxy` always uses the bridge), HEMNET_WS_PORT (Localhost port of the fetchproxy concentrator the ContextMint Bridge extension connects to (default 37149). Every MCP on one machine shares it, so move it for all of them or not at all), FETCHPROXY_WS_HOST (Bind interface for the fetchproxy concentrator, a literal IP only (default 127.0.0.1). Keep on loopback; it exists for hosted deployments that run each MCP in its own network namespace), FETCHPROXY_IDENTITY_DIR (Absolute path where the fetchproxy long-term identity keypair is stored (default ~/.fetchproxy/identity/)).