Configure MCP Server

Overview

The Red Bricks Model Context Protocol (MCP) server provides a standardized JSON-RPC 2.0 interface for AI models (like Claude, ChatGPT, or Gemini) to programmatically query the Red Bricks database. This allows your AI agents to fetch real-time project data, construction details, and more.

What is the MCP Server?

The MCP server acts as a gateway to a wide range of AI tools and services, allowing users to perform complex operations with ease. It supports secure and efficient communication, ensuring that all transactions are authenticated and authorized. By connecting to the MCP server, users can unlock capabilities such as real-time data interactions, advanced application development, and enhanced data processing.

Connect with Claude (OAuth2)

The easiest way to connect is through Claude's built-in connector support with OAuth2 authentication.

Quick Setup

In Claude, open Settings and navigate to Connectors
Click Add Connector and enter:
- Name: Red Bricks
- Address: https://api.redbricksdata.com/mcp/server
Ignore the advanced settings section and click Add
Log in with your Red Bricks credentials to confirm
You will be sent back to Claude with everything connected

Requirements

An active Red Bricks subscription on the Agent or Enterprise tier
A Red Bricks user account with team membership

Example Prompts

Once connected, you can ask Claude things like:

"Show me all selling condos in Toronto under $800K"
"Find projects by Tridel with available floorplans"
"What are the price trends in Liberty Village?"
"Compare floorplans for project 6809"

Step-by-Step Connection Guide (Bearer Token)

1. Authentication

All requests require a Bearer Token.

Navigate to your API Settings Page
Generate a new MCP Access Token.
Include this token in the header of every request.

2. Set Up Your Request

All requests to the MCP server should be sent to the following base URL:

POST https://api.redbricksdata.com/mcp/server

3. Configure Headers

Include the following headers in your request:

Authorization: Bearer <access_token>
Content-Type: application/json

Replace <access_token> with your actual token. The word Bearer and the following space are required.

4. Request Format

The MCP server uses the JSON-RPC 2.0 protocol. Ensure your request is formatted as follows:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list-projects",
    "arguments": {
      "city": "Toronto",
      "page": 1
    }
  }
}

5. Send the Request

Use the POST method to send your request to the server.

Troubleshooting Common Issues

Invalid Token: Ensure your token is correct and not expired.