Onehome Mcp
Query OneHome (CoreLogic) listings, photos, and saved homes from Claude while researching relocation, office space, or real-estate-adjacent product ideas.
Overview
OneHome MCP is a Build-phase-adjacent Idea/research MCP server that lets Claude search OneHome (CoreLogic), read property details and photos, and manage saved homes using token, magic-link, or browser-capture auth.
What is this MCP server?
- Search OneHome inventory and pull property details and photos into agent threads
- Manage saved homes without leaving Claude Code or Cursor
- Authenticate via ONEHOME_TOKEN JWT, agent ONEHOME_MAGIC_LINK, or fetchproxy capture-from-tab mode
- Optional ONEHOME_WS_PORT override (default 37149) when using browser capture
- stdio npm package onehome-mcp v0.9.0 for local MCP registration
- Package version 0.9.0
- Transport: stdio via npm registryType
- Default fetchproxy WebSocket port 37149 (ONEHOME_WS_PORT override)
What problem does it solve?
Switching between your agent and the OneHome portal breaks flow when you need fast answers on listings, photos, and saved inventory.
Who is it for?
Builders with legitimate OneHome portal access who want listing research and saved-home checks inside Claude-driven workflows.
Skip if: Teams needing official MLS/CoreLogic API contracts, bulk scraping without portal rights, or fully headless setup without any signed-in session path.
What do I get? / Deliverables
After you register onehome-mcp, Claude can run OneHome searches and saved-home actions through MCP tools with your chosen auth mode.
- Registered stdio MCP server for OneHome search and property detail tools
- Agent-callable access to photos and saved homes using your auth mode
- Optional fetchproxy tab-capture path when ONEHOME_TOKEN and ONEHOME_MAGIC_LINK are unset
Recommended MCP Servers
Journey fit
Property and market discovery happens before you commit to a geography or a vertical—canonical shelf is early journey research, not production ops. Search, detail, and saved-home tools support structured research on comps and inventory rather than shipping code.
How it compares
Browser-session real-estate MCP bridge, not a standalone property-research skill or public MLS API.
Common Questions / FAQ
Who is onehome-mcp for?
Solo builders and agents with OneHome access who want Claude to search listings, fetch details and photos, and work with saved homes via MCP.
When should I use onehome-mcp?
Use it during idea and market research when you need OneHome data in the same thread as notes, comps, and product decisions—before you commit to a location or RE feature set.
How do I add onehome-mcp to my agent?
Install the npm package onehome-mcp, add a stdio MCP entry pointing at that binary, set ONEHOME_TOKEN or ONEHOME_MAGIC_LINK (or use capture mode with portal tab open), then restart Claude Code, Cursor, or your MCP client.