mcp

This MCP server exposes a set of Repliers API tools via a Model Context Provider (MCP) interface. It enables natural language style prompts to be translated into concrete API calls against the Repliers MLS data, including live listings, advanced search filters, property details, historical data, and analytics. Tools available include search (core query engine with flexible filters), get-a-listing (detailed property information), find-similar-listings (comparisons based on location and attributes), get-address-history (listing history by address), property-types-styles (reference data for MLS boards), get-deleted-listings (recently removed MLS listings), areas-cities-and-neighborhoods (geographic catalog), buildings (building metadata), and more. You can compose messages in Claude Desktop or any MCP client to perform complex real estate queries without managing backend MLS integrations.

To use the server, connect your MCP client to the running node process (via the command and arguments specified in the configuration). Start by ensuring you have a valid REPLIERS_API_KEY in your environment or .env file, then issue MCP requests that target the available tools (e.g., search with location and price filters, or get-a-listing with a MLS number). Testing with Postman is also supported using the provided endpoints and the mcpServer.js entry point.

Prerequisites:

• Node.js v18+ (v22+ recommended)
• npm (comes with Node.js)

1. Prepare your environment

• Create a project directory and place the MCP server code (including mcpServer.js) in it.
• Create an .env file (optional if you prefer environment variables directly). Ensure you have a valid REPLIERS_API_KEY from your Repliers account.

2. Install dependencies From the project root, run:

npm install

3. Configure environment variables Create a file named .env at the project root and add:

REPLIERS_API_KEY=your-repliers-api-key

4. Run the MCP server Start the server with Node:

node mcpServer.js

If you need Server-Sent Events support, you can run with the --sse flag:

node mcpServer.js --sse

5. Optional: Test with Postman or Claude

• Use the Postman steps in the README to connect to the MCP server and verify tool availability.
• In Claude Desktop, add a new MCP server using the absolute path to node and the mcpServer.js script as described in the documentation.

Tips and known considerations:

• Ensure REPLIERS_API_KEY is kept secret; store it in a secure .env file or secret manager.
• When integrating with Claude Desktop, provide absolute paths to node and mcpServer.js to avoid version resolution issues.
• For production deployments, you can containerize using Docker as shown in the README (Dockerfile is provided in the project).
• If you enable SSE (--sse), clients can listen for real-time stream updates for supported endpoints.
• The tools list in the MCP server includes: search, get-a-listing, find-similar-listings, get-address-history, property-types-styles, get-deleted-listings, areas-cities-and-neighborhoods, and buildings. Use the CLI or index.js tools command to audit available tools and their parameters.
• Review the tools’ individual behavior in the tools directory to see how environment variables and API keys are consumed.
• When testing with Postman, set the MCP request type to STDIO and use the absolute path to the node executable and mcpServer.js as described in the documentation.