Onehome 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 onehome-mcp -- npx -y onehome-mcp

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

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

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

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

Optional settings from the registry entry, left out of the block above: ONEHOME_TOKEN (Bearer token for services.onehome.com. Paste the raw JWT (Authorization header value, minus the 'Bearer ' prefix) from your signed-in portal.onehome.com session), ONEHOME_MAGIC_LINK (Magic-link URL with ?token=... from your real-estate agent. The MCP extracts the token query param and uses it directly as the bearer), ONEHOME_WS_PORT (Override the fetchproxy WebSocket port (default 37149). Only used when ONEHOME_TOKEN / ONEHOME_MAGIC_LINK are unset and the MCP boots in capture-from-tab mode), ONEHOME_COMMUNITIES_FILE (Path to a JSON array of community names used for feature extraction; overrides the built-in Lake Lure / mountain-NC default vocabulary), 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/)).