MCP server

The Matchai MCP server lets an AI assistant search the listings that real estate professionals have published on Matchai, open one listing, and look up a broker. MCP, the Model Context Protocol, is the open standard assistants use to call outside tools.

The server is public and read-only. It needs no account, no API key and no sign-in, and it returns published data only.

EndpointsCopy link to this section

TransportCopy link to this section

The server speaks MCP over Streamable HTTP, in its stateless form, with JSON-RPC 2.0 messages.

• POST one JSON-RPC message to the endpoint. A request gets 200 with an application/json body. A notification gets 202 with no body.
• No sessions. The server issues no Mcp-Session-Id and remembers nothing between requests, so any request can be answered on its own. Follow the standard handshake anyway, so your client also works with other servers.
• No event stream. GET and DELETE answer 405, which is the correct answer for a server with nothing to push. OPTIONS answers 204 for CORS.
• No batches. Send one message per request. An array is refused with -32600.
• Protocol versions: 2025-11-25, 2025-06-18 and 2025-03-26. initialize returns your version when the server speaks it, and the latest otherwise. If you send an MCP-Protocol-Version header after initialize, it must be one of these, or the request fails with 400.
• Size. A request body can be up to 256 KB.

The server answers these methods:

Any other method answers -32601 (method not found). The server has no prompts, logging or completion features.

serverInfo.name is matchai-listings and serverInfo.version is a semantic version. It changes when a tool or field is added or changes shape.

Access, data and limitsCopy link to this section

• Authentication. None. /.well-known/mcp.json declares authentication.required: false, and the server asks for no key, token or sign-in.
• Data. Published listings, and the public profile of brokers who have published a site, a Matchai Page or a business card. A broker's phone number and email address appear only when they are published on that business card.
• Order of results. By relevance to the request and by how recently the listing was updated. No broker can pay to change the order or to be included.
• Rate limit. Each calling address can make 600 tools/call requests per minute. Above that, the call returns a tool result with isError: true and a message asking you to try again in a minute. The limit applies to tools/call only. It is an abuse guard, set high enough that a busy assistant host does not reach it.
• CORS. Open to every origin, so browser-based tools such as the MCP Inspector work. The server reads no cookie and no credential. Preflight answers are cacheable for 24 hours.
• Caching. Responses are sent with Cache-Control: no-store.

Discovery documentsCopy link to this section

Matchai publishes machine-readable descriptions of the server. All are JSON, send an ETag, honour If-None-Match, and allow cross-origin reads.

Broker sites and Matchai Pages serve their own copies of these documents. They point to the same MCP server on matchai.co.

Connect an assistantCopy link to this section

ClaudeCopy link to this section

To add the server to Claude Code from a terminal:

claude mcp add --transport http matchai https://matchai.co/mcp

ChatGPTCopy link to this section

Other clientsCopy link to this section

Most clients that support remote MCP servers accept a URL in a configuration file:

{
  "mcpServers": {
    "matchai": {
      "url": "https://matchai.co/mcp"
    }
  }
}

Clients that ask for a transport type should use Streamable HTTP, with no authentication.

Call the server from your own codeCopy link to this section

The examples use curl. Each request is a single JSON-RPC message.

curl -s https://matchai.co/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2025-11-25",
      "capabilities": {},
      "clientInfo": { "name": "my-client", "version": "0.1.0" }
    }
  }'

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "protocolVersion": "2025-11-25",
    "capabilities": { "tools": {}, "resources": {} },
    "serverInfo": {
      "name": "matchai-listings",
      "title": "Matchai",
      "version": "1.0.0",
      "websiteUrl": "https://matchai.co"
    },
    "instructions": "Matchai is a real estate platform where licensed brokers in Québec and across Canada publish their listings. …"
  }
}

curl -s -i https://matchai.co/mcp \
  -H "Content-Type: application/json" \
  -d '{ "jsonrpc": "2.0", "method": "notifications/initialized" }'

curl -s https://matchai.co/mcp \
  -H "Content-Type: application/json" \
  -d '{ "jsonrpc": "2.0", "id": 2, "method": "tools/list" }'

curl -s https://matchai.co/mcp \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 3,
    "method": "tools/call",
    "params": {
      "name": "search_listings",
      "arguments": { "query": "3 bedroom condo in Laval under 600k", "limit": 3 }
    }
  }'

ErrorsCopy link to this section

Problems with the message itself are JSON-RPC errors. Problems a model can fix, such as a bad argument or a URL that matches no listing, come back as a tool result with isError: true and a message the model can read.