360 Ghar - Real Estate MCP Server

What is 360 Ghar - Real Estate MCP Server?

A high-performance backend for the 360 Ghar unified real estate platform. It powers three integrated modules: a real estate marketplace with swipe-based property discovery, a short-stay booking system (360 Stays), and a comprehensive property management system. Built with FastAPI and PostgreSQL (PostGIS), it exposes its functionality through an HTTP API and a Model Context Protocol (MCP) server for AI assistants.

How to use 360 Ghar - Real Estate MCP Server?

Set up a Python 3.12+ environment with Docker, clone the repository, install dependencies using uv sync, configure environment variables (Supabase Auth, database), start the database services, apply migrations, and optionally load seed data. Then run the application with uv run python run.py or fastapi dev. The MCP HTTP server is available for AI assistant integration.

Key features of 360 Ghar - Real Estate MCP Server

• Tinder-like property swiping (like/pass)
• Unified property search with geospatial and full-text filtering
• Property visit scheduling with agent coordination
• Short-stay booking with dynamic pricing and guest management
• Tenant, lease, and rent collection management
• Maintenance requests and financial reporting
• MCP HTTP server for AI assistant access

Use cases of 360 Ghar - Real Estate MCP Server

• Building a real estate marketplace with intuitive property discovery
• Implementing short-term rental booking and management
• Providing property management tools for landlords and agents
• Enabling AI assistants to query and act on property data via MCP

FAQ from 360 Ghar - Real Estate MCP Server

What runtime dependencies are required?

Python 3.12+, Docker, Docker Compose, and a Supabase project for authentication.

How is authentication handled?

Clients authenticate directly with Supabase Auth (phone-first, email optional). The backend expects an Authorization: Bearer token for protected routes.

Which database and geospatial support does it use?

PostgreSQL with PostGIS extension, accessed via async SQLAlchemy 2.0+ and GeoAlchemy2.

How can I access the API documentation?

Automatic API documentation is provided by FastAPI (Swagger UI and ReDoc) when the server is running.

What transport does the MCP server use?

The MCP server uses HTTP; details are described in the MCP HTTP Server section of the README.