Setting Up Repliers MCP
Repliers MCP connects the Repliers API to AI assistants like ChatGPT and Claude, enabling you to leverage all of Repliers' features through natural language — including property searches, market analytics, listing history, and more.
There are two ways to use Repliers MCP:
- Hosted MCP — connect directly to
https://mcp.repliers.iowith no server setup required - Open Source / Self-hosted — run your own instance using the Repliers MCP Server on GitHub
Step 1: Link Your API Key to MCP
Before connecting any MCP client, you need to authorize a Repliers API key for use with MCP.
- Sign in to the Repliers Developer Portal
- Find the API key you want to use and click the MCP icon next to it
- That key is now linked to Repliers MCP
Option A: Hosted MCP Server
The hosted MCP server at https://mcp.repliers.io is the fastest way to get started — no installation or local server required.
Connecting via Claude.ai
- In Claude.ai, open Settings and navigate to the Connectors or Integrations section
- Choose Add custom connector (or equivalent option for adding an MCP server)
- Enter the hosted MCP URL:
https://mcp.repliers.io - Save the connector
- When prompted, sign in to your Repliers account to authorize the connection
Once connected, Claude will have access to all Repliers MCP tools in your conversations.
Connecting via Claude Desktop
- Open Claude Desktop and go to Settings → Developers → Edit Config
- Add the following to your
mcpServersconfiguration:
{
"mcpServers": {
"repliers": {
"url": "https://mcp.repliers.io"
}
}
}
- Save and restart Claude Desktop
- When prompted, sign in to your Repliers account to authorize the connection
- Confirm the Repliers MCP server shows a green indicator in the Developers settings
Connecting via ChatGPT
- In ChatGPT, go to Settings → Connectors (or your workspace's app/plugin management area)
- Select Add a custom connector or MCP Server
- Enter the hosted MCP URL:
https://mcp.repliers.io - Save the configuration
- When prompted, sign in to your Repliers account to complete authorization
Option B: Open Source / Self-Hosted MCP Server
If you prefer to run your own MCP server — for example, in a production environment or to customize the toolset — you can use the open source version.
Prerequisites
- Node.js v18 or higher (v22+ recommended)
- npm (included with Node.js)
- A Repliers API key
Installation
1. Clone the repository
git clone https://github.com/Repliers-io/mcp-server.git
cd mcp-server
2. Install dependencies
npm install3. Configure your API key
Create a .env file in the project root:
REPLIERS_API_KEY=your-repliers-api-key
Testing with Postman (Optional but Recommended)
Before connecting to an AI client, you can verify your server is working using the Postman Desktop App.
- Download Postman Desktop
- Create a new MCP Request
- Set the type to
STDIOand the command to:
node /absolute/path/to/mcpServer.js
To find the absolute path, run:
realpath mcpServer.js
- Click Connect — you should see a list of available Repliers tools
Connecting to Claude Desktop
- Get the absolute paths to your
nodebinary andmcpServer.js:
which node
realpath mcpServer.js
- Open Claude Desktop → Settings → Developers → Edit Config and add:
{
"mcpServers": {
"repliers": {
"command": "/absolute/path/to/node",
"args": ["/absolute/path/to/mcpServer.js"],
"env": {
"REPLIERS_API_KEY": "your-repliers-api-key"
}
}
}
}
- Save and restart Claude Desktop
- Confirm the Repliers server has a green indicator under Settings → Developers
node to ensure Claude Desktop uses Node v18+. You can check your version with node --version.Docker Deployment (Production)
For production use, Docker is recommended for reliability and isolation.
1. Build the image
docker build -t repliers-mcp .
2. Add to Claude Desktop config
{
"mcpServers": {
"repliers-mcp": {
"command": "docker",
"args": [
"run", "-i", "--rm",
"--env-file=.env",
"repliers-mcp"
]
}
}
}
Make sure your .env file contains your REPLIERS_API_KEY.
Running with SSE Support
To run the server with Server-Sent Events (SSE) instead of STDIO:
node mcpServer.js --sse
Configuring NLP for Listing Search
The search-listings tool works differently from most MCP tools — instead of relying on the AI assistant to structure the API request, it passes your natural language query directly to Repliers' own NLP endpoint. This approach was chosen because it produces significantly more accurate results: Repliers' NLP layer understands MLS-specific terminology, normalizes values to match MLS® standards, and supports context-aware conversational searches.
Because the NLP endpoint is powered by OpenAI, you must link a valid OpenAI API key to your Repliers API key before search-listings will work.
How to Enable NLP Search
- Sign in to the Repliers Developer Portal
- Select the API key you have linked to MCP
- Edit the key settings and locate the NLP Search option
- Enter your OpenAI API key and save
Once configured, the search-listings tool will accept natural language queries and automatically convert them into structured Repliers API requests.
What NLP Search Can Do
- Natural language to structured queries — "Find me a condo in Toronto with at least 1 bedroom in the Annex with underground parking" is automatically converted into the correct Repliers API parameters
- Context-aware conversations — follow-up prompts refine the previous search without starting over (e.g., "Also, my budget is $500k and I need at least 1 parking spot")
- AI image search integration — visual preferences like "white kitchen" or "open concept living room" are incorporated into the search
- MLS® data normalization — user-friendly terms are mapped to valid MLS® values (e.g., "enclosed balcony" →
balcony=encl)
Available Tools
Once connected, your AI assistant can use the full suite of Repliers tools, organized by category:
Listings
Tool | Description |
|---|---|
| Search active, sold, or leased listings with flexible filters (price, location, type, beds/baths, keywords, and more) |
| Fetch detailed information for a specific listing by MLS number |
| Return listings similar to a given property by location, price, or type |
| Retrieve full MLS listing history for a specific address |
| Retrieve valid values for listing search parameters |
| Access market statistics and analytics |
Locations & Buildings
Tool | Description |
|---|---|
| Search geographic locations supported by the Repliers API |
| Autocomplete location queries for search inputs |
| Search building-level data for condos, apartments, and complexes |
| Fetch detailed information about a specific building |
Agents, Members & Brokerages
Tool | Description |
|---|---|
| Search for agents |
| Retrieve details for a specific agent |
| Create a new agent record |
| Update an existing agent record |
| Delete an agent record |
| Search for MLS members |
| Search for brokerages |
| Search for offices |
Clients
Tool | Description |
|---|---|
| Search for clients |
| Retrieve details for a specific client |
| Create a new client record |
| Update an existing client record |
| Delete a client record |
Saved Searches
Tool | Description |
|---|---|
| List all saved searches |
| Retrieve a specific saved search |
| Create a new saved search |
| Update an existing saved search |
| Delete a saved search |
| List listings matching a saved search |
| Retrieve a specific saved search match |
| Update a saved search match |
Favorites
Tool | Description |
|---|---|
| List favorited listings |
| Remove a listing from favorites |
Estimates
Tool | Description |
|---|---|
| List property estimates |
| Create a new property estimate |
| Update an existing estimate |
| Delete an estimate |
Messaging & NLP
Tool | Description |
|---|---|
| List messages |
| Retrieve a specific message |
| Send a message |
| List NLP chat sessions |
| Retrieve NLP search history |
Example Prompts
- "Find 3-bedroom apartments in San Francisco under $1 million listed in the last week"
- "Send listing alerts to my client john doe when 4 bedroom homes in austin hit the market"
- "Give me the listing history for 123 Main St, San Francisco"
- "What's the median list price for residential homes in Austin, aggregated by month over the last 18 months?"
Troubleshooting
The MCP server isn't showing as connected
Make sure you've linked an API key in the Repliers Developer Portal (Step 1 above). Only one key can be active at a time.
Claude Desktop falls back to an old Node version
Use the absolute path to your Node binary (from which node) rather than just node in your config.
I'm being asked to sign in on every connection
Ensure you're completing the Repliers sign-in flow fully. If the issue persists, try unlinking and re-linking your API key in the Developer Portal.
Tools aren't appearing in Claude
Restart Claude Desktop after editing the config file. Confirm the server has a green status indicator under Settings → Developers.
Additional Resources
- Repliers Developer Portal
- Repliers MCP Server on GitHub
- Repliers API Documentation
- Create a Repliers Account
Updated on: 20/05/2026
Thank you!
