constellation1-mcp-server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@constellation1-mcp-server find active properties in Seattle under 1 million"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Constellation 1 MCP Server
A Model Context Protocol (MCP) server that provides comprehensive access to Constellation 1 real estate data APIs. This server enables LLMs to perform property searches, agent research, market analysis, and media retrieval through RESO (Real Estate Standards Organization) standardized interfaces.
Features
π Comprehensive Real Estate Data - Access to Properties, Agents, Offices, Media, and Market Analytics
π Advanced Property Search - Full OData querying with filtering, sorting, and field selection
π€ Agent & Office Discovery - Complete MLS member and brokerage information
πΈ Media & Marketing Assets - Property photos, videos, virtual tours, and documents
π Market Analytics - Days on market, pricing trends, and historical data
π Enterprise Security - OAuth2 authentication with automatic token management
π Rich Resources - Built-in field reference and query examples accessible via MCP
β‘ Performance Optimized - Dynamic metadata parsing, intelligent caching, and response optimization
Related MCP server: MLIT Geospatial MCP Server
Quick Start
1. Get Constellation 1 API Credentials
Contact your RESO API provider to obtain Constellation 1 API access
Obtain your client credentials (client_id and client_secret)
Ensure you have access to the required RESO endpoints
2. Configure MCP Client
Add the server to your MCP client configuration:
Cursor
Add to your Cursor MCP settings (~/.cursor/mcp.json or through Command Palette > Open MCP Settings > New MCP Server):
{
"mcpServers": {
"constellation1": {
"command": "npx",
"args": ["-y", "constellation1-mcp-server"],
"env": {
"CONSTELLATION1_CLIENT_ID": "your-client-id-here",
"CONSTELLATION1_CLIENT_SECRET": "your-client-secret-here"
}
}
}
}Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"constellation1": {
"command": "npx",
"args": ["constellation1-mcp-server"],
"env": {
"CONSTELLATION1_CLIENT_ID": "your-client-id-here",
"CONSTELLATION1_CLIENT_SECRET": "your-client-secret-here"
}
}
}
}Other MCP Clients
# Set environment variables
export CONSTELLATION1_CLIENT_ID="your-client-id-here"
export CONSTELLATION1_CLIENT_SECRET="your-client-secret-here"
# Run the server
npx constellation1-mcp-serverAvailable Tools
Real Estate Data
reso_query- Query RESO entities with full OData supportreso_help- Get field references, examples, and best practices
Usage Examples
Find Active Properties in Seattle
{
"tool": "reso_query",
"arguments": {
"entity": "Property",
"filter": "StandardStatus eq 'Active' and City eq 'Seattle'",
"select": "ListingKey,ListPrice,BedroomsTotal,BathroomsTotal,UnparsedAddress,PublicRemarks",
"orderby": "ListPrice asc",
"top": 25
}
}Get Property with Marketing Photos
{
"tool": "reso_query",
"arguments": {
"entity": "Property",
"filter": "StandardStatus eq 'Active' and PhotosCount gt 0",
"expand": "Media($filter=MediaCategory eq 'Photo' and Permission ne 'Private';$orderby=Order asc;$top=5)",
"select": "ListingKey,ListPrice,UnparsedAddress,PhotosCount",
"top": 10
}
}Find Real Estate Agent
{
"tool": "reso_query",
"arguments": {
"entity": "Member",
"filter": "MemberFullName eq 'John Smith'",
"select": "MemberMlsId,MemberFullName,MemberEmail,MemberDirectPhone,OfficeName,MemberDesignation"
}
}Get Market Analysis Data
{
"tool": "reso_query",
"arguments": {
"entity": "Property",
"filter": "StandardStatus eq 'Closed' and CloseDate ge 2024-01-01",
"select": "ListingKey,ClosePrice,CloseDate,BedroomsTotal,LivingArea,City,DaysOnMarket",
"orderby": "CloseDate desc",
"top": 100
}
}Get Help and Examples
{
"tool": "reso_help",
"arguments": {
"topic": "examples"
}
}Configuration
Environment Variables
CONSTELLATION1_CLIENT_ID(required) - Your Constellation 1 OAuth client IDCONSTELLATION1_CLIENT_SECRET(required) - Your Constellation 1 OAuth client secret
Optional Configuration
CONSTELLATION1_BASE_URL(optional, default:https://listings.cdatalabs.com/odata) - API base URLCONSTELLATION1_AUTH_URL(optional, default:https://authenticate.constellation1apis.com/oauth2/token) - OAuth token endpoint
Alternative Environment Variable Names
The server also supports these alternative environment variable names:
CLIENT_ID/CLIENT_SECRETRESO_CLIENT_ID/RESO_CLIENT_SECRET
API Quotas and Usage
This server accesses RESO-compliant real estate data through the Constellation 1 API. Monitor your API usage and ensure compliance with your RESO API provider's terms of service.
Resources
The server provides built-in MCP resources with documentation and examples:
constellation1://docs/field-reference- Comprehensive RESO field reference guideconstellation1://docs/quick-start- Common query patterns and examples
Access these through your MCP client's resource interface.
Error Handling
The server returns structured errors with helpful context:
{
"error": {
"code": "AUTH_FAILED",
"message": "OAuth2 authentication failed: 401 Unauthorized",
"context": {
"endpoint": "https://authenticate.constellation1apis.com/oauth2/token",
"status": 401
}
}
}Common error codes:
INVALID_ENTITY- Unsupported RESO entity typeAUTH_FAILED- OAuth2 authentication failedAPI_ERROR- RESO API request failedSKIP_LIMIT_EXCEEDED- Pagination skip limit exceededMETADATA_FETCH_FAILED- Unable to load RESO metadata
Security
API credentials are never logged or exposed in responses
Input validation prevents injection attacks through Zod schemas
OAuth2 tokens are securely cached and automatically refreshed
All API communication uses HTTPS with proper certificate validation
Development
Building from Source
git clone https://github.com/david-pivonka/constellation1-mcp-server.git
cd constellation1-mcp-server
npm install
npm run buildTesting
npm testUsing MCP Inspector
npm run build
CONSTELLATION1_CLIENT_ID="your-client-id" CONSTELLATION1_CLIENT_SECRET="your-client-secret" npx @modelcontextprotocol/inspector ./dist/index.jsContributing
Contributions are welcome! Please submit pull requests to our GitHub repository.
License
MIT License - see LICENSE file for details.
Available Tools
2 toolsreso_helpA
Get comprehensive RESO field reference documentation, query examples, and best practices. This tool provides instant access to field guides, entity descriptions, filter patterns, and common use cases for effective RESO API usage.
Inputs: topic (required).
reso_queryB
Query the RESO (Real Estate Standards Organization) API for comprehensive real estate data. This tool provides access to MLS (Multiple Listing Service) data including property listings, agent information, office details, media files, and market analytics. Perfect for real estate research, market analysis, property searches, and lead generation. Supports advanced filtering, sorting, and field selection with standardized RESO field names for consistent data access across different MLS systems.
Inputs: top, skip, entity, expand, +6 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 2 tools
reso_query is the execution tool for actual data retrieval and filtering, while reso_help provides documentation, field references, and query examples. There is no functional overlap, so an agent can clearly choose between acting and learning.
Both tools use the consistent reso_ prefix followed by a clear action word, creating a predictable pattern. Even though the set is small, the naming is uniform and easy to infer.
Two tools is a minimal surface for a broad RESO API domain. Both tools earn their place, but the server feels slightly thin rather than fully fleshed out for the range of data it claims to access.
The read-only query workflow is well covered: reso_query handles all entity searches, filtering, sorting, and field selection, while reso_help provides the necessary reference and examples. There are no obvious missing operations for the stated purpose.
Maintenance
Related MCP Connectors
US property search and full listing detail (Redfin-sourced) as agent tools.
Real estate data for AI agents: property lookup, comps, search, skip tracing, phone/address checks
AI-native real estate discovery with structured property search and market intelligence.
Zillow MCP for AI agents: property data, Zestimates & listings β 300+ fields per home. Free tier.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI applications to search and analyze UNLOCK MLS real estate data through Bridge Interactive's RESO Web API, supporting natural language property searches, market analysis, and agent discovery.2-
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to search and retrieve Japanese real estate data through unified access to the MLIT Real Estate Information Library API, supporting over 25 geospatial datasets for interactive queries.191MIT

Repliers MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceProvides AI assistants access to real-time MLS data via the Repliers API, enabling natural language property search, market statistics, and listing details.512 npm21MIT- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to look up real estate agents, search MLS listings, submit buyer/seller leads, and access proprietary seller-intent signals in SC and GA.MIT