360 Ghar - Real Estate MCP Server

What is 360 Ghar - Real Estate MCP Server?

A high-performance FastAPI backend that powers the 360 Ghar unified real estate platform. It serves three integrated modules: a real estate marketplace with swipe‑based discovery, a short‑stay booking system for hotels and vacation rentals, and a comprehensive property management system for landlords and property managers.

How to use 360 Ghar - Real Estate MCP Server?

Clone the repository, install dependencies with uv sync or pip, copy .env.example to .env with your Supabase and database credentials, start PostgreSQL and Redis via Docker Compose, run database migrations with supabase db push, optionally load sample data, then start the application with uv run python run.py or uv run fastapi dev app/main.py --port 3600 --host 0.0.0.0. The API is then available at http://localhost:3600.

Key features of 360 Ghar - Real Estate MCP Server

• Tinder‑like property swiping for discovery
• Geospatial, full‑text, and filtered property search
• Agent‑managed visit scheduling with load balancing
• Short‑stay booking with dynamic pricing
• Tenant, lease, and rent collection management
• Financial reporting and document vault
• Asynchronous architecture with FastAPI and PostgreSQL/PostGIS
• Secure authentication via Supabase Auth (phone‑first)

Use cases of 360 Ghar - Real Estate MCP Server

• Buyers and renters discovering properties via swipe and map‑based search
• Users scheduling property visits coordinated with agents
• Travelers booking short‑stay accommodations with availability checks
• Landlords managing tenants, leases, maintenance requests, and rent collection
• Property managers generating financial reports and storing documents

FAQ from 360 Ghar - Real Estate MCP Server

What technologies does it use?

The tech stack includes FastAPI, PostgreSQL with PostGIS, SQLAlchemy 2.0 async, Pydantic, Supabase Auth, optional Redis caching, Sentry for observability, and Docker.

How is authentication handled?

Clients authenticate directly with Supabase Auth SDK using phone as primary method. The backend expects an Authorization: Bearer <supabase_access_token> header for protected routes.

Does it support Docker?

Yes. Full Docker and Docker Compose support is provided for development – databases can be started with docker-compose up -d db redis.

What is the MCP HTTP server?

The backend exposes Model Context Protocol (MCP) HTTP servers for AI assistants and MCP‑based integrations, as described in the “MCP HTTP Server” section.

What database does it use?

PostgreSQL with the PostGIS extension for geospatial queries, managed via SQLAlchemy and Supabase migrations.