Assam Dag Parcels (Bhuvan)
RemoteAbout Assam Dag Parcels (Bhuvan)
Assam Dag Parcels (Bhuvan) is an MCP server for location-based research on cadastral parcels in Assam, for people examining land boundaries and nearby plots. It uses the Bhuvan cadastral layer to return dag numbers, areas and map images; it does not provide owner or patta details.
Key features
- 01Find parcels by coordinates
- 02Return dag numbers and areas
- 03List nearby parcels by radius
- 04Show satellite or street map images
- 05Provide parcel boundaries as GeoJSON
Use cases
- 01Identify the dag at a map point
- 02Review parcels around a location
- 03View labelled parcel map images
MCP support
It exposes parcel search and parcel-image tools to MCP clients. Search results can include parcel records and, on request, boundaries in GeoJSON.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://bumiatlas.com/mcp/assamclaude mcp add --transport http bumiatlas-assam-dag-parcels https://bumiatlas.com/mcp/assam{"mcpServers":{"bumiatlas-assam-dag-parcels":{"type":"http","url":"https://bumiatlas.com/mcp/assam"}}}Open in Cursor{"servers":{"bumiatlas-assam-dag-parcels":{"type":"http","url":"https://bumiatlas.com/mcp/assam"}}}Open in VS Code{"mcpServers":{"bumiatlas-assam-dag-parcels":{"type":"http","url":"https://bumiatlas.com/mcp/assam"}}}{"mcpServers":{"bumiatlas-assam-dag-parcels":{"serverUrl":"https://bumiatlas.com/mcp/assam"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEAssam Land Parcels & Dag Number Lookup MCP (অসম)
Connect your AI assistant (Claude, ChatGPT, Cursor) to BumiAtlas for land research in Assam through the Model Context Protocol (MCP).
- Cadastral parcels across Assam from ISRO Bhuvan's Assam cadastral layer, each with its dag number and outline area
- Lookup by coordinates: the parcel at a point, then its neighbours within a radius
- Satellite and street map images of a parcel and its neighbours, labelled by dag number
The source has the dag number only: no village (mouza), circle, patta number or owner, so parcels are found by location, not by number.
Connect
https://bumiatlas.com/mcp/assam
Add it as a custom connector in any MCP client and sign in with Google; no API key. Tools, examples and data notes: bumiatlas.com/mcp-docs/assam.
- Claude: Settings → Connectors → Add custom connector, paste the URL, then Connect.
- ChatGPT: Settings → Apps & Connectors → Advanced → Developer mode, then Create with the URL and OAuth authentication.
These are BumiAtlas's India tools, so parcels in the other loaded states can be looked up too.
Tools
| Tool | Description |
|---|---|
IN_parcel_search | Find parcels by latitude, longitude, ULPIN, or khasra/survey number with state and village; each result is the whole record, the boundary as GeoJSON on request |
IN_parcel_image | Satellite or street map image of a parcel or point, with every parcel in view outlined and labelled with its khasra, survey or dag number |
Example prompts
- "Which dag is at 26.1445, 91.7362 in Guwahati, and how big is it?"
- "Show a satellite image of the dag parcels around 26.1445, 91.7362."
- "List the parcels within 100 m of this point in Assam."
Compared with the official portals
If you look up land on Dharitree or Bhunaksha Assam, this gives an AI assistant the map side of that lookup: which dag is where, how big it is, and its neighbours. It has no jamabandi, patta or owner details; use Dharitree for those. BumiAtlas is not affiliated with the Government of Assam.
Data source
Bhuvan (ISRO / NRSC), Assam cadastral layer. Parcels from the state land-record portals, compiled by datameet / ramSeraph indian_cadastrals (CC0). A copy of public data for research, not a legal land record.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.