OneHome (CoreLogic) real-estate access for Claude — search, property details, photos, saved homes
OneHome (CoreLogic) real-estate access for Claude — search, property details, photos, saved homes
Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (23/23 approved).
7 files analyzed · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Set these up before or after installing:
Environment variable: ONEHOME_TOKEN
Environment variable: ONEHOME_MAGIC_LINK
Environment variable: ONEHOME_WS_PORT
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-chrischall-onehome-mcp": {
"env": {
"ONEHOME_TOKEN": "your-onehome-token-here",
"ONEHOME_WS_PORT": "your-onehome-ws-port-here",
"ONEHOME_MAGIC_LINK": "your-onehome-magic-link-here"
},
"args": [
"-y",
"onehome-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
MCP server for OneHome (CoreLogic) — search the listings your real-estate agent curated for you, fetch property details + photos, compare houses side-by-side, and run mortgage / affordability math from within Claude.
Sister project to zillow-mcp, redfin-mcp, compass-mcp, and homes-mcp. Same tool ergonomics — different upstream auth model.
This project was developed and is maintained by AI (Claude). Use at your own discretion.
OneHome isn't a public listings site. Buyers usually reach it through a magic link an agent emails them — https://portal.onehome.com/...?token=eyJ.... That token query param IS the per-user bearer that the portal SPA hands to every GraphQL request.
So instead of routing every fetch through your signed-in browser tab (like the other realty MCPs), onehome-mcp talks directly to services.onehome.com/graphql from Node, with Authorization: Bearer <jwt> attached. We support three ways to source that bearer:
| Mode | How to enable | Notes |
|---|---|---|
env_token | ONEHOME_TOKEN=<jwt> | Paste the raw bearer from devtools Network panel. Most direct. |
magic_link | ONEHOME_MAGIC_LINK=https://portal.onehome.com/...?token=... | Paste the full URL your agent sent — we extract the token param. |
fetchproxy_capture | (no env) + fetchproxy extension installed + signed-in portal.onehome.com tab | We wait for your tab to fire any GraphQL request, snapshot the Authorization header, and reuse it. |
| Tool | What it does |
|---|---|
onehome_get_user | Smallest auth probe — returns your OneHome profile (name, email, locale). |
onehome_get_groups | List the OneHome "groups" your agent has shared with you (each one a market / curated listing bucket). |
onehome_get_group_details | Inspect a single group by id. |
onehome_get_saved_searches | List a group's saved-search definitions. searchCriteria is JSON-parsed when possible. |
onehome_search_properties | Listings within a group; optionally scoped to a saved search. |
onehome_search_suggestions | Free-text suggestion search (address, MLS #) across all feeds. |
onehome_get_property | Full property record by listing id or portal URL. |
onehome_get_property_photos | Full media gallery — Thumbnail / Medium / Large variants + room descriptions. |
onehome_compare_properties | 2-8 listings side-by-side. Per-row error capture; calls are concurrent. |
onehome_get_schools | Local-Logic primary + high schools near a lat/lng. |
onehome_get_walk_score | Local-Logic walk / transit / bike / car friendliness scores. |
onehome_graphql | Power-user escape hatch — send a raw GraphQL document with variables. |
onehome_calculate_mortgage | Local PITI calculator. Same math as the other realty MCPs. |
onehome_calculate_affordability | Local 28/36 DTI solver — max home price you can afford. |
onehome_healthcheck | End-to-end auth + GraphQL smoke check with token-expiry diagnostics. |
The simplest path is the published Claude plugin (.mcpb install). For local dev:
git clone https://github.com/chrischall/onehome-mcp
cd onehome-mcp
npm install
npm run build
Then point your MCP host at node /abs/path/to/onehome-mcp/dist/bundle.js with one of:
// claude_desktop_config.json
{
"mcpServers": {
"onehome-mcp": {
"command": "node",
"args": ["/abs/path/to/onehome-mcp/dist/bundle.js"],
"env": {
"ONEHOME_MAGIC_LINK": "https://portal.onehome.com/en-US/properties/map?token=eyJ..."
}
}
}
}
npm test # vitest, mocked transport, no network
npm run test:watch
npm run test:coverage
npx tsc --noEmit
npm run build # tsc --noEmit + esbuild → dist/bundle.js
Tests use a FakeTransport (in tests/helpers.ts) that registers per-operationName handlers — there's no live network in the test suite. The tests/index.test.ts smoke check loads the same tool registrations src/index.ts uses against an in-memory MCP client/server pair, so "I wrote the tool file but forgot to wire it up" mistakes fail loudly.
MIT.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.