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": {
      "args": [
        "-y",
        "onehome-mcp"
      ],
      "command": "npx"
    }
  }
}

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

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

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

This one needs environment variables set before it will start: 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.). The author declared them in the registry entry; get the values from the project itself.