mcpField
O
onehome-mcp

onehome-mcp

Local
github.com/chrischallBusiness & Marketing1Updated 2d ago

About onehome-mcp

onehome-mcp is an MCP server for buyers using agent-shared OneHome listings. It retrieves listing data and photos, compares properties, and provides mortgage and affordability calculations.

Key features

  1. 01Browse agent-shared groups and saved searches
  2. 02Search listings and resolve addresses
  3. 03Retrieve property records and photo galleries
  4. 04Compare 2–8 properties
  5. 05Calculate mortgage and affordability estimates

Use cases

  1. 01Review homes in an agent-curated search
  2. 02Find a listing from an address or MLS number
  3. 03Compare shortlisted properties side by side
  4. 04Estimate mortgage payments or an affordable price

MCP support

It exposes OneHome search, listing, comparison, and calculation tools to MCP clients. Authentication can use a bearer token, a magic link, or a captured browser session.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"chrischall-onehome": {
"command": "npx",
"args": [
"-y",
"onehome-mcp"
],
"env": {
"ONEHOME_TOKEN": "<ONEHOME_TOKEN>",
"ONEHOME_MAGIC_LINK": "<ONEHOME_MAGIC_LINK>",
"ONEHOME_WS_PORT": "<ONEHOME_WS_PORT>",
"ONEHOME_COMMUNITIES_FILE": "<ONEHOME_COMMUNITIES_FILE>",
"FETCHPROXY_WS_HOST": "<FETCHPROXY_WS_HOST>",
"FETCHPROXY_IDENTITY_DIR": "<FETCHPROXY_IDENTITY_DIR>"
}
}
}
}
Run commandnpx -y onehome-mcp
Environment variables to set
ONEHOME_TOKENSecretBearer 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_LINKMagic-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_PORTOverride 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_FILEPath to a JSON array of community names used for feature extraction; overrides the built-in Lake Lure / mountain-NC default vocabulary.
FETCHPROXY_WS_HOSTBind 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_DIRAbsolute path where the fetchproxy long-term identity keypair is stored (default ~/.fetchproxy/identity/).

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmonehome-mcp1.1.10

Tools

21

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
viewenumNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact strips image/avatar URLs from the response; "full" returns OneHome's payload untouched. No field projection: this server has no verified record of which OneHome fields matter, and inventing one would risk dropping a field a caller needs.compact | full

Details

From the project README

onehome-mcp

CI npm license

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.

What's different about OneHome

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:

ModeHow to enableNotes
env_tokenONEHOME_TOKEN=<jwt>Paste the raw bearer from devtools Network panel. Most direct.
magic_linkONEHOME_MAGIC_LINK=https://portal.onehome.com/...?token=...Paste the full URL your agent sent — we extract the token param.
fetchproxy_capture(no env) + ContextMint Bridge browser extension installed (Chrome: load the release's chrome zip unpacked; Safari isn't available yet — it will ship inside the ContextMint app, so use Chrome for now) + signed-in portal.onehome.com tabWe wait for your tab to fire any GraphQL request, snapshot the Authorization header, and reuse it.

ContextMint Bridge is the fetchproxy browser extension under its new name, from the same maintainer — fetchproxy's own README (fetchproxy#extension) points to it. Its source is public at nullnet-app/contextmint-bridge: build it yourself, or check a release zip against the .sha256 file published beside it (shasum -a 256 -c contextmint-bridge-chrome-<version>.zip.sha256).

Tools

ToolWhat it does
onehome_get_userSmallest auth probe — returns your OneHome profile (name, email) and the groups your agent shared.
onehome_get_groupsList the OneHome "groups" your agent has shared with you (each one a market / curated listing bucket).
onehome_get_saved_searchFetch an agent-curated saved search by id — name, filter criteria, polygon, and the OSK listing ids that compose the share.
onehome_get_saved_search_with_listingsThe "show me my saved homes" flow in one round trip — saved search plus its inflated listings.
onehome_search_propertiesListings within a group; optionally scoped to a saved search.
onehome_search_suggestionsFree-text suggestion search (address, MLS #) across all feeds.
onehome_get_by_addressResolve a single free-text street address to a listing's portal URL + id.
onehome_resolve_addressesBulk-resolve up to 100 structured addresses to portal URLs + listing ids; concurrent, per-row error capture.
onehome_get_propertyFull property record by listing id or portal URL.
onehome_bulk_getFetch up to N listings in one call — one structured row per id, per-row error capture.
onehome_get_property_photosFull media gallery — Thumbnail / Medium / Large variants + room descriptions.
onehome_compare_properties2-8 listings side-by-side. Per-row error capture; calls are concurrent.
onehome_get_schoolsLocal-Logic primary + high schools near a lat/lng.
onehome_get_walk_scoreLocal-Logic walk / transit / bike / car friendliness scores.
onehome_graphqlPower-user escape hatch — send a raw read-only GraphQL document (queries only; mutations and subscriptions are refused) with variables.
onehome_calculate_mortgageLocal PITI calculator. Same math as the other realty MCPs.
onehome_calculate_affordabilityLocal 28/36 DTI solver — max home price you can afford.
onehome_set_authAdd another authenticated session at runtime (magic link / JWT / email-token) for buyers holding shares across multiple agents.
onehome_set_active_sessionForce a specific registered session to be the active one (overrides MLS-suffix routing).
onehome_get_session_contextList every registered session — auth mode, token expiry, and the group / saved-search / agent scope each bootstrapped.
onehome_healthcheckEnd-to-end auth + GraphQL smoke check with token-expiry diagnostics.

Install

The simplest path is the published Claude plugin (.mcpb install). Its settings take an optional OneHome magic link or bearer token (both stored as sensitive values); leave both blank to use browser-bridge capture instead. 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..."
      }
    }
  }
}

Development

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.

License

MIT.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.