# CREHQ Location Intelligence [Health: Active]

**Category:** 🏠 Real Estate  
**Repository:** https://github.com/groundroof/crehq-mcp-server  
**GitHub Stars:** 0  
**npm Downloads (last month):** 141  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/crehq-location-intelligence

## Description
CREHQ chain-location tools for brands, sites, franchise data, credit signals, and whitespace.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "crehq-location-intelligence": {
    "command": "npx",
    "args": ["-y","crehq-mcp-server"],
    "env": {
      "CREHQ_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `CREHQ_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What CREHQ Location Intelligence MCP server does

CREHQ Location Intelligence MCP server connects MCP-compatible AI clients to CREHQ’s location-intelligence API. It covers multi-unit and franchise brands, storefronts, ownership, site-level tenancy, FDD information, credit signals, location events, and geographic trends. The connector is a thin API wrapper: it does not maintain its own database or change records in CREHQ.

The affiliation resolver can assess a venue URL, name, or address and return an evidence-backed status such as branded, independent, non-commercial, or unresolved. Where available, it identifies the canonical brand, operator, and parent company. Other tools support brand discovery, location searches, nearby-radius queries, bulk location retrieval, historical occupancy, and changes over time.

## How it works

The server authenticates requests with a CREHQ API key and forwards them to the production REST base at `https://crehq.com/wp-json/crehq/v1`. It can run locally over MCP stdio or be accessed through CREHQ’s hosted MCP endpoint at `https://mcp.crehq.com/mcp`.

The catalog includes tools for companies, locations, affiliation, history, datasets, and trends. Premium operations include whitespace analysis, co-tenancy, modeled site profiles, observed site patterns, and recent location context. CREHQ’s backend applies the permissions and limits associated with the key. When a request is outside the key’s entitlement, the response can provide an upgrade or purchase path rather than exposing the restricted data.

## Setup and configuration

A local installation requires Node.js 18 or newer and the `CREHQ_API_KEY` environment variable. The published package can be started with:

```bash
CREHQ_API_KEY=crehq_live_xxxxx npx crehq-mcp-server
```

For a source build, clone the repository, run `npm install`, compile with `npm run build`, and start `node dist/index.js` with the key in the environment. The repository also provides a test script that checks six read endpoints against the live API.

Free sandbox keys are issued through CREHQ’s developer page and include bounded usage. Pro, dataset, Intelligence, and Enterprise access provide different limits and data rights. Claude Desktop can launch the npm package as a stdio server, while other stdio-capable clients can run the same command or the compiled entry point. Remote clients can use the hosted MCP URL and authorize with the key.

## Tools and capabilities

CREHQ Location Intelligence MCP server includes tools for:

- Searching and retrieving company profiles, ownership, franchise economics, real-estate criteria, contacts, and credit signals.
- Listing, searching, retrieving, geospatially querying, and bulk-loading locations.
- Reading location events, individual site histories, company changes, past occupancy, and address timelines.
- Comparing geographic concentration and brand-level outlet, fee, or financial trends.
- Accessing dataset catalogs, downloads, purchased snapshots, and rows from eligible purchased datasets.
- Routing upgrade requests and providing a controlled intelligence preview for eligible Pro keys.

## Limitations and notes

Free and Pro credentials do not expose every tool or field. Usage limits, row budgets, resolver quotas, and monthly preview allowances are enforced by CREHQ. Premium intelligence and dataset access may require separate licensing, and redistribution or embedded-use rights are not implied by API access.

The three modeled site-profile routes may return HTTP 404 while production approval is pending. Their results must be treated as CREHQ-modeled outputs based on observed location and context data, not as company-stated requirements unless the response includes explicit provenance. A checkout does not upgrade the current credential in place; a newly issued Pro key must be installed before retrying.

_Full upstream README: https://allmcps.com/mcp/crehq-location-intelligence/readme_