onehome-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ONEHOME_TOKEN | No | Direct JWT bearer token from OneHome portal. | |
| ONEHOME_MAGIC_LINK | No | Full magic link URL from your agent; token is extracted from query parameter. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| onehome_get_userA | Returns the OneHome user profile + the consumer-share groups attached. For full agent / registered users, queries the GraphQL |
| onehome_get_groupsA | List the OneHome groups your agent has shared with you. For full agent / registered users, returns the GraphQL |
| onehome_get_session_contextA | Returns one entry per registered session — its |
| onehome_get_saved_searchA | Fetch the agent-curated saved search by its id (UUID). Returns the search's name, filter criteria ( |
| onehome_get_saved_search_with_listingsA | Combo tool: the "show me my saved homes" flow in a single round trip. Internally runs |
| onehome_search_propertiesA | Fetch listings inside a OneHome consumer-share. Two modes:
Both args default from the MCP's bootstrapped session context (the magic-link checkToken response) when neither is passed explicitly. Sort is Listings here are returned via the GraphQL listing-card projection, which does NOT include |
| onehome_search_suggestionsA | Cross-feed suggestion search by address, MLS number, or partial query. Bypasses the group/saved-search structure and hits the global suggestion endpoint — useful for "find an address" or "look up by MLS number". Returns id, address parts, beds/baths, list price, thumbnail per match. Inflate any result with |
| onehome_get_propertyA | Fetch full details for a single OneHome listing by id or portal URL. Returns address, list / close / previous price, $/sqft, beds/baths/sqft, lot size (raw |
| onehome_get_property_photosA | Fetch the full media gallery for a OneHome listing. Returns one entry per image with Thumbnail / Medium / Large CDN URLs, dimensions, the listing-room description (LongDescription), and display order. Pass either |
| onehome_compare_propertiesA | Fetch 2 or more OneHome listings and align their facts side-by-side. Each target may supply |
| onehome_bulk_getA | Fetch up to 200 OneHome listings in a single call. Returns one structured row per input id (no side-by-side summary table — use |
| onehome_get_schoolsA | Fetch the Local-Logic school data for a coordinate — separate primary and high-school lists, each entry with name, attributes (types/grades/programs/levels), and proximity (walking distance + straight-line distance). Returns an |
| onehome_get_walk_scoreA | Local-Logic location scores for a coordinate — pedestrian / car / cycling / transit friendliness, plus proximity summaries for groceries, restaurants, parks, primary + high schools. Each score is a |
| onehome_graphqlA | Power-user escape hatch — send a raw GraphQL document with variables. Returns the whole |
| onehome_calculate_mortgageA | Local-only mortgage payment calculator. Returns a full PITI breakdown (principal + interest, property tax, insurance, HOA, PMI) and total interest over the life of the loan. No network call. Provide either |
| onehome_calculate_affordabilityA | Solve for the maximum home price you can afford under the standard 28/36 DTI rule. Inputs: monthly income, recurring monthly debts (car/student loans), down payment, interest rate, optional property-tax rate / insurance / HOA / loan term. Output: max home price, binding constraint (front-end vs back-end), and the PITI breakdown at that price. Same math as zillow-mcp / redfin-mcp / compass-mcp / homes-mcp. No network — pure local math. |
| onehome_healthcheckA | Round-trip a minimal authenticated query through the configured transport. Picks |
| onehome_get_by_addressA | Resolve a free-text street address (with optional city/state/zip) to a OneHome listing's canonical portal URL and id in one call. Walks a 2-rung ladder: (1) |
| onehome_resolve_addressesA | Resolve up to 100 structured addresses to OneHome canonical portal URLs + listing OSK ids in one call. Each input is a |
| onehome_set_authA | Provide a magic-link URL, a raw JWT bearer, or an email-token to ADD another authenticated session to the MCP — useful when a buyer holds shares across multiple agents/MLSes (one magic link per share). The MCP detects the input shape (URL → extract |
| onehome_set_active_sessionA | Force a specific registered session to be the active one. Useful when MLS-suffix routing picks the wrong session (e.g. a free-text search across multiple MLSes, or a listing without a |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 21 tools
Most tools target a distinct resource and action, but a few overlap notably: onehome_get_saved_search, onehome_get_saved_search_with_listings, and onehome_search_properties all deal with saved searches/listings, and onehome_get_by_address vs onehome_resolve_addresses are near-identical single vs bulk versions. The detailed descriptions clarify the differences, so an agent can select correctly, but the boundaries are not always immediately obvious.
The overwhelming majority follow the onehome_<verb>_<noun> pattern (onehome_get_property, onehome_search_properties, onehome_set_active_session). Minor deviations exist: onehome_healthcheck, onehome_graphql, and onehome_bulk_get do not fit the verb_noun pattern, and address resolution uses two different verbs (get_by vs resolve) for the same concept. Overall, the naming is predictable and readable, with only a few outliers.
21 tools is on the heavier end of the calibration range, but each tool serves a distinct function within a broad real-estate domain, covering property search, details, photos, comparisons, schools, walk scores, mortgage math, address resolution, session management, and an escape hatch. The count feels justified rather than bloated, though a few tools (e.g., the separate bulk_get and compare_properties) could arguably be merged.
The tool surface covers the core consumer workflow: searching/fetching listings, resolving addresses, retrieving property details/photos, schools, walk scores, and mortgage calculations/affordability. Missing lifecycle operations (create/update/delete) are not applicable to this read-only domain, and the onehome_graphql escape hatch ensures any uncovered GraphQL operation is still possible. Minor gaps include no direct way to fetch listing history or agent info, but these are not fundamental to the stated purpose.