constellation1-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLIENT_ID | No | Alternative for CONSTELLATION1_CLIENT_ID | |
| CLIENT_SECRET | No | Alternative for CONSTELLATION1_CLIENT_SECRET | |
| RESO_CLIENT_ID | No | Alternative for CONSTELLATION1_CLIENT_ID | |
| RESO_CLIENT_SECRET | No | Alternative for CONSTELLATION1_CLIENT_SECRET | |
| CONSTELLATION1_AUTH_URL | No | OAuth token endpoint (default: https://authenticate.constellation1apis.com/oauth2/token) | |
| CONSTELLATION1_BASE_URL | No | API base URL (default: https://listings.cdatalabs.com/odata) | |
| CONSTELLATION1_CLIENT_ID | No | Your Constellation 1 OAuth client ID | |
| CONSTELLATION1_CLIENT_SECRET | No | Your Constellation 1 OAuth client secret |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| reso_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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| RESO Field Reference Guide | Comprehensive guide to RESO fields, entities, enums, filter patterns, and best practices for AI-friendly real estate data queries |
| RESO Query Quick Start | Quick reference for common RESO query patterns and examples organized by use case |
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.