BhoomiAI UP Geo MCP Server

# BhoomiAI UP Geo API

BhoomiAI is an MVP geospatial intelligence system for Uttar Pradesh. It turns a city name or latitude/longitude into sourced local facts such as district, elevation, nearby roads, nearby water, and an AI answer grounded in those facts.

Live Demo

Open the deployed UI:

https://bhoomiai-up-geo.onrender.com/

API docs:

https://bhoomiai-up-geo.onrender.com/docs

The hosted demo uses bring-your-own OpenAI key mode. Users can enter their own key in the UI for LLM answers, or use the app without a key for local/template answers.

The product has three working surfaces:

Frontend UI -> FastAPI
MCP server  -> FastAPI
LLM answer  -> local geo facts first, OpenAI answer second

Related MCP server: geocontext

What It Solves

Land and location decisions in India often require checking scattered GIS datasets manually. This MVP gives one simple interface for questions like:

Which district is this coordinate in?
What is the elevation here?
How close is the nearest road or waterbody?
Would this coordinate be risky for building a school?
What data is available for this point?

The language model is not allowed to invent geospatial values. The backend fetches facts first, then the LLM explains only what those facts support.

Features

• Static web UI served by FastAPI.

• Clickable Leaflet map for selecting latitude/longitude.

• City/place geocoding from a local UP gazetteer.

• District lookup from Census 2011 district boundaries.

• Elevation lookup from SRTM HGT tiles.

• Road/water/place proximity from an OpenStreetMap sample extract.

• /v1/ask endpoint with optional OpenAI answer generation.

• Local stdio MCP server for VS Code Copilot and other MCP clients.

Run Locally

From the project folder:

cd <ABSOLUTE_PATH_TO_REPO>
.\.venv\Scripts\Activate.ps1
pip install -r requirements.txt
.\.venv\Scripts\python.exe -m uvicorn app.main:app --reload --port 8002

Open the web UI:

http://127.0.0.1:8002/

Open the API docs:

http://127.0.0.1:8002/docs

If you cloned the repo fresh, create the virtual environment first:

python -m venv .venv
.\.venv\Scripts\Activate.ps1
pip install -r requirements.txt

Environment

Create .env from .env.example:

OPENAI_API_KEY=your_real_key_here
OPENAI_MODEL=gpt-4.1-mini
OPENAI_LLM_ENABLED=true
UP_GEO_API_BASE_URL=http://127.0.0.1:8002

Important:

.env is private and ignored by git.
.env.example is safe to commit.

If OPENAI_LLM_ENABLED=false or no valid key is present, /v1/ask returns a local template answer instead of an LLM-written answer.

Bring Your Own OpenAI Key

For public demos, do not deploy with your personal OPENAI_API_KEY. The UI includes an optional OpenAI API key field. When a user enters their own key:

Browser -> X-OpenAI-API-Key header -> /v1/ask or /v1/report -> OpenAI

The key is stored only in the browser session storage and is not written to project files or server storage. If no key is provided, the app uses the local template answer fallback.

API Endpoints

Health

GET /health

Geocode

POST /v1/geocode

Example:

{
  "query": "Kanpur",
  "limit": 3
}

Fetch Facts

POST /v1/fetch

Example:

{
  "lat": 26.4499,
  "lng": 80.3319,
  "fields": [
    "district",
    "elevation_m",
    "nearest_road_distance_m",
    "nearest_water_distance_m",
    "nearest_water_name",
    "nearest_place_name"
  ]
}

Ask Question

POST /v1/ask

Example:

{
  "lat": 26.4499,
  "lng": 80.3319,
  "question": "Would this coordinate be risky for building a school? Mention only what the data supports."
}

Flow:

question
  -> deterministic field planner
  -> local geospatial resolvers
  -> sourced facts
  -> OpenAI answer if enabled
  -> template fallback if LLM is unavailable

Generate Site Report

POST /v1/report

Example:

{
  "lat": 26.4499,
  "lng": 80.3319,
  "question": "Generate a site report for this coordinate."
}

Returns a structured report with location, summary, available fields, unavailable fields, facts, citations, and report_markdown.

Deploy on Render

This repo includes render.yaml for deploying the FastAPI app as a Render Web Service.

Render settings:

Build Command: pip install -r requirements.txt
Start Command: uvicorn app.main:app --host 0.0.0.0 --port $PORT
Health Check Path: /health
Python version: 3.11.11

Current Render URL:

https://bhoomiai-up-geo.onrender.com

That URL opens the BhoomiAI frontend UI because the FastAPI app serves app/static/index.html at /.

No project OpenAI key is required on Render. The deployed UI supports bring-your-own-key: each visitor can enter their own OpenAI API key in the browser, and the app sends it only with /v1/ask and /v1/report requests. The server does not store it.

Notes:

The ignored OSM sample file is not deployed to Render.
District lookup and committed SRTM tiles will work.
Road/water/place proximity needs the OSM sample file or a hosted data store.

MCP Server

The MCP server exposes BhoomiAI as tools for AI clients.

Tools:

up_geo_geocode(query, limit=5)
up_geo_fetch(lat, lng, fields)
up_geo_ask(lat, lng, question)
up_geo_report(lat, lng, question optional)

Current MCP behavior:

up_geo_geocode -> POST /v1/geocode
up_geo_fetch   -> POST /v1/fetch
up_geo_ask     -> POST /v1/ask
up_geo_report  -> POST /v1/report

That means the FastAPI server must be running before the MCP client calls tools.

Start FastAPI first:

cd <ABSOLUTE_PATH_TO_REPO>
.\.venv\Scripts\python.exe -m uvicorn app.main:app --reload --port 8002

Then configure your MCP client.

VS Code Copilot MCP Config

Use this shape for VS Code/Copilot. Replace <ABSOLUTE_PATH_TO_REPO> with your local clone path.

{
  "servers": {
    "bhoomiai-up-geo": {
      "type": "stdio",
      "command": "<ABSOLUTE_PATH_TO_REPO>\\.venv\\Scripts\\python.exe",
      "args": [
        "<ABSOLUTE_PATH_TO_REPO>\\mcp_server.py"
      ],
      "cwd": "<ABSOLUTE_PATH_TO_REPO>"
    }
  }
}

Generic MCP Config

Some MCP clients use mcpServers instead of servers:

{
  "mcpServers": {
    "bhoomiai-up-geo": {
      "command": "<ABSOLUTE_PATH_TO_REPO>\\.venv\\Scripts\\python.exe",
      "args": [
        "<ABSOLUTE_PATH_TO_REPO>\\mcp_server.py"
      ],
      "cwd": "<ABSOLUTE_PATH_TO_REPO>"
    }
  }
}

A clone-safe version is also in mcp_config.example.json.

Data Currently Integrated

District Boundaries

Files:

data/vector/2011_Dist.shp
data/vector/2011_Dist.shx
data/vector/2011_Dist.dbf
data/vector/2011_Dist.prj

Source:

DataMeet India Districts Census 2011
https://github.com/datameet/maps/tree/master/Districts/Census_2011

Used by:

district
location.district
location.inside_service_area

Elevation

Files:

data/raster/srtm/N26E080.hgt.gz
data/raster/srtm/N25E082.hgt.gz
data/raster/srtm/N28E077.hgt.gz

Source:

SRTM DEM via AWS elevation-tiles-prod
https://s3.amazonaws.com/elevation-tiles-prod/skadi/

Used by:

elevation_m

Current downloaded tile coverage:

N26E080: Lucknow/Kanpur area
N25E082: Varanasi area
N28E077: Noida area

OSM Sample Data

File:

data/vector/osm_up_samples.geojson

Contains sample data for roads, water, and places around selected areas such as Lucknow, Varanasi, Noida, Agra, and Gorakhpur depending on the downloaded sample.

Used by:

nearest_road_distance_m
nearest_water_distance_m
nearest_water_name
nearest_place_name

Local Gazetteer

File:

data/vector/up_places.json

Used by:

/v1/geocode
up_geo_geocode
city buttons and search-style workflows

Large Data Note

data/vector/osm_up_samples.geojson is generated local data and is larger than GitHub's normal single-file limit. It is ignored by git. After cloning, regenerate or download the OSM sample data with the script in scripts/ before using road/water/place proximity features.

Known Limitations

• This is an MVP, not a legal land record system.

• OSM road/water/place coverage is sample coverage, not full Uttar Pradesh coverage yet.

• Flood risk, soil, parcel ownership, and official land-use classification are not integrated yet.

• Elevation coverage only works where SRTM tiles have been downloaded.

• LLM answers are explanations of available facts, not independent survey or legal advice.

Next Steps

Recommended build order:

1. Add a Generate Site Report button in the UI.

2. Download remaining SRTM tiles for full UP elevation coverage.

3. Replace sample OSM GeoJSON with a full Uttar Pradesh OSM extract.

4. Add a flood/water-risk dataset.

5. Add soil or land-use/land-cover data.

6. Move large geospatial data into PostGIS for faster nearest-neighbor queries.

7. Prepare GitHub release notes and deployment instructions.