CREHQ MCP Server
Related Servers
Alternatives to CREHQ MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables local AI-powered retail location intelligence by exposing database schema and spatial query tools to LLMs. It supports executing validated SQL, retrieving example spatial analyses, and generating strategic business insights from retail siting data.-
- AlicenseAqualityBmaintenanceEnables AI assistants to answer mortgage-related queries by providing tools for lender search, loan limit lookup, down-payment assistance programs, and more, with data sourced from real wholesale lenders and broker-curated intel.88 npmMIT
- AlicenseAqualityCmaintenanceEnables LLMs to access Constellation 1 real estate data APIs for property searches, agent research, and market analytics through RESO standardized interfaces.211 npm1MIT
- AlicenseNot gradedqualityDmaintenanceProvides live commercial real estate data (rates, demographics) and analysis tools (DCF, rent roll parsing, lease abstraction, IC memo generation) within Claude Desktop.1MIT

Lofty MCP Serverofficial
AlicenseCqualityCmaintenanceEnables AI agents to interact with Lofty CRM via natural language, providing 120 tools across 22 modules for full API coverage.10018 npmElastic 2.0- AlicenseNot gradedqualityBmaintenanceEnables AI agents to access live Zillow property data, Zestimates, and listings for over 160 million U.S. homes.1MIT
TDQS
Scored across 33 tools
Each tool targets a distinct resource and operation: locations, companies, datasets, trends, and intelligence. While there are multiple history/event tools (location_history, site_timeline, locations_events, company_changes), their descriptions clarify by scope: single entity vs. site succession vs. cross-brand stream vs. brand-scoped changes. Some overlap exists but overall the boundaries are clear.
The dominant pattern is 'crehq_<resource>_<action>' (e.g., locations_list, company_get), but there are notable deviations like crehq_request_upgrade, crehq_whitespace, crehq_co_tenancy, and crehq_intelligence_preview. Also inconsistent singular/plural usage (location_get vs locations_list, company_get vs companies_list). The naming is readable but not fully uniform.
33 tools is a large surface for an MCP server. While each tool has a distinct function, the sheer number may overwhelm agents and increase selection effort. Some tools could be consolidated (e.g., dataset list/categories/download, or merging company_changes with locations_events).
The domain is well-covered for a read-only commercial real estate data platform: location lookup and search, brand and franchise intelligence, historical timelines and site succession, point-in-time occupancy, datasets, trends, and premium analyses like whitespace and co-tenancy. No obvious dead ends; only minor gaps like write operations (not expected) or direct location-to-company-contact cross-references.