Quick Answer
The Realie MCP server is a Streamable HTTP Model Context Protocol endpoint at https://app.realie.ai/api/mcp that exposes live U.S. property lookup tools to IDE agents and chat hosts. MCP clients usually authenticate with Clerk OAuth; compatible hosts may also send a Realie API key as Bearer authorization. Each successful property tool call consumes one token from your monthly Realie allowance, and list tools return up to 10 properties per call.
Summary
Use this server for property records—not the documentation MCP at https://docs.realie.ai/mcp. Published tools map to Realie REST endpoints: address_lookup, property_search, parcel_lookup, location_search, owner_search, and comparables. initialize and tools/list work without credentials; tools/call returns 401 with WWW-Authenticate metadata until the host completes sign-in.
Step by step
- 1
Choose the product MCP URL
Register https://app.realie.ai/api/mcp as a Streamable HTTP MCP server in your host. Do not use https://docs.realie.ai/mcp for property data.
- 2
Authenticate with OAuth (typical IDE hosts)
Let the host complete Clerk OAuth using protected-resource metadata at https://app.realie.ai/.well-known/oauth-protected-resource/mcp. New accounts add a payment method at https://app.realie.ai/developer before property calls succeed.
- 3
Authenticate with an API key (supported hosts)
When the host documents remote MCP with authorization headers, send Authorization: Bearer YOUR_REALIE_API_KEY. OAuth client registration in the Clerk dashboard is not required for customers.
- 4
List tools, then call one
Run tools/list to see address_lookup, property_search, parcel_lookup, location_search, owner_search, and comparables. Call address_lookup or property_search to verify access.
- 5
Track token usage
Each successful tools/call uses one token shared across Platform and API usage. Sign-in failures (HTTP 401) and error results (isError: true, such as not found or an account or billing denial) do not consume a token. See https://www.realie.ai/pricing for plan allowances.
MCP tools and REST endpoints
address_lookup → GET /api/public/property/address
property_search → GET /api/public/property/search
parcel_lookup → GET /api/public/property/parcelId
location_search → GET /api/public/property/location
owner_search → GET /api/public/property/owner
comparables → GET /api/public/premium/comparables (premium tier)
Example prompts (address-based lookups)
“Call address_lookup for 504 Lavaca St, Austin, TX and return JSON fields for year built and assessed value.”
“Use property_search with state FL, city Orlando, and address containing Fairhaven to find matching parcels.”
“After address_lookup for 100 Main St, Nashville, TN, call comparables if the host supports premium tools.”
What it does not return
Realie returns county-sourced property records, not MLS listing feeds, listing photos, or active for-sale inventory from broker systems.
Field availability varies by county and source office. An empty or partial record means the jurisdiction did not publish that attribute for the parcel, not that the connection failed.
The documentation MCP at https://docs.realie.ai/mcp searches Mintlify help pages only. It cannot return live property records.
Sources
Frequently asked questions
- How much does each MCP tool call cost?
- One token per successful tool call. Sign-in failures (HTTP 401) and error results (isError: true), including access denials and empty lookups, do not spend a token. A successful search call costs one token for the whole page of results. Through MCP, property_search, location_search, owner_search and comparables return up to 10 properties per call (page with cursor or offset), so 100 properties is about 10 tokens; REST and the CLI return up to 100 per page.
- Where is the MCP server card?
- JSON metadata is at https://app.realie.ai/api/mcp/server-card and https://www.realie.ai/.well-known/mcp/server-card.json.
- Does OAuth create an API key?
- No. OAuth identifies your Clerk user for MCP. The CLI command realie login uses the same OAuth window and then stores your existing API key for REST and CI.