Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Citiwise is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
7
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
UDCPR 2020 (Maharashtra) feasibility for a plot, with the clause behind every number.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http citiwise-mcp https://citiwise.in/mcp
# 2 — ask your agent for something these tools do
# feasibility, compare_uses, check_design and 4 more
Citiwise costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
TEAll 1 server
tejasdgurav1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http citiwise-mcp https://citiwise.in/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Use this when someone asks what they can build on a plot or piece of land anywhere in Maharashtra outside Greater Mumbai: FSI or FAR, built-up area, setbacks (margins), height, how many floors, parking or approvals under UDCPR 2020, the building rules for every town in the state. Do not use for Greater Mumbai, for land prices or for building permission itself. Returns the UDCPR feasibility of one
| Parameter | Type | Required | Notes |
|---|---|---|---|
| town | string | yes | Maharashtra town, city or planning authority, e.g. Pune, Kolhapur, Nashik, PMRDA |
| area | number | yes | plot area in m2: the least of 7/12, measurement sheet and site (1 sq ft = 0.0929 m2; 1 guntha = 101.17 m2; 1 acre = 4,046.86 m2) |
| road | number | no | width of the road in front in m, when there is one road and no sides (1 ft = 0.3048 m) |
| sides | array | no | every side, anticlockwise, starting at a road |
| zone | string | no | nc non-congested, c congested (gaothan) |
| land_use | string | no | — |
| road_widening | number | no | — |
| reservation | number | no | — |
| handed_over | boolean | no | — |
| stilt | boolean | no | — |
| ground_height | number | no | — |
| floor_height | number | no | — |
| units | array | no | the unit mix, one entry per type, e.g. [{"type":"2 BHK","count":12,"carpet":60},{"type":"Shop","count":4,"carpet":25}]; parking takes each type in its own Table 8-B row; a count left out is worked out |
| flats | integer | no | number of flats; with carpet, a one-type unit mix |
| carpet | number | no | carpet area of a flat, m2 |
| polygon | array | no | plot corners [x, y] in m, anticlockwise, one per side, side 1 first; needed for plots that are not rectangles |
| sprinklers | boolean | no | mixed building fully sprinklered (1.3(93)(xiv) note) |
| power_line_kv | number | no | voltage of an overhead line near the plot, kV, for its clearance |
| tod | boolean | no | plot inside a TOD zone (14.2.1) |
| road_widening_side | integer | no | side number (1-based) that the road widening strip comes off; default the first road side |
Use this when someone wants to know which uses are allowed on a plot in Maharashtra, or how built-up differs between uses on the same land. Returns every use on the same land in a fixed order: allowed or the reason not, conditions, clause, and built-up with and without TDR.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| town | string | yes | Maharashtra town, city or planning authority, e.g. Pune, Kolhapur, Nashik, PMRDA |
| area | number | yes | plot area in m2: the least of 7/12, measurement sheet and site (1 sq ft = 0.0929 m2; 1 guntha = 101.17 m2; 1 acre = 4,046.86 m2) |
| road | number | no | width of the road in front in m, when there is one road and no sides (1 ft = 0.3048 m) |
| sides | array | no | every side, anticlockwise, starting at a road |
| zone | string | no | nc non-congested, c congested (gaothan) |
| land_use | string | no | — |
| road_widening | number | no | — |
| reservation | number | no | — |
| handed_over | boolean | no | — |
| stilt | boolean | no | — |
| ground_height | number | no | — |
| floor_height | number | no | — |
| units | array | no | the unit mix, one entry per type, e.g. [{"type":"2 BHK","count":12,"carpet":60},{"type":"Shop","count":4,"carpet":25}]; parking takes each type in its own Table 8-B row; a count left out is worked out |
| flats | integer | no | number of flats; with carpet, a one-type unit mix |
| carpet | number | no | carpet area of a flat, m2 |
| polygon | array | no | plot corners [x, y] in m, anticlockwise, one per side, side 1 first; needed for plots that are not rectangles |
| sprinklers | boolean | no | mixed building fully sprinklered (1.3(93)(xiv) note) |
| power_line_kv | number | no | voltage of an overhead line near the plot, kV, for its clearance |
| tod | boolean | no | plot inside a TOD zone (14.2.1) |
| road_widening_side | integer | no | side number (1-based) that the road widening strip comes off; default the first road side |
Use this when someone has a proposed building on a plot in Maharashtra and wants to know whether it meets UDCPR. Checks a proposal's built-up, height and margins (one per side, in side order) against UDCPR, with allowed, proposed and pass or fail per item. Margins need the height or the upper floors with them.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| town | string | yes | Maharashtra town, city or planning authority, e.g. Pune, Kolhapur, Nashik, PMRDA |
| area | number | yes | plot area in m2: the least of 7/12, measurement sheet and site (1 sq ft = 0.0929 m2; 1 guntha = 101.17 m2; 1 acre = 4,046.86 m2) |
| road | number | no | width of the road in front in m, when there is one road and no sides (1 ft = 0.3048 m) |
| sides | array | no | every side, anticlockwise, starting at a road |
| zone | string | no | nc non-congested, c congested (gaothan) |
| land_use | string | no | — |
| road_widening | number | no | — |
| reservation | number | no | — |
| handed_over | boolean | no | — |
| stilt | boolean | no | — |
| ground_height | number | no | — |
| floor_height | number | no | — |
| units | array | no | the unit mix, one entry per type, e.g. [{"type":"2 BHK","count":12,"carpet":60},{"type":"Shop","count":4,"carpet":25}]; parking takes each type in its own Table 8-B row; a count left out is worked out |
| flats | integer | no | number of flats; with carpet, a one-type unit mix |
| carpet | number | no | carpet area of a flat, m2 |
| polygon | array | no | plot corners [x, y] in m, anticlockwise, one per side, side 1 first; needed for plots that are not rectangles |
| sprinklers | boolean | no | mixed building fully sprinklered (1.3(93)(xiv) note) |
| power_line_kv | number | no | voltage of an overhead line near the plot, kV, for its clearance |
| tod | boolean | no | plot inside a TOD zone (14.2.1) |
| road_widening_side | integer | no | side number (1-based) that the road widening strip comes off; default the first road side |
Use this when someone asks what a specific UDCPR regulation or table says. Returns the UDCPR text of a regulation or table by its number, such as '6.2.6', '11.2.4' or 'Table 6-G'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ref | string | yes | — |
Use this when someone asks where UDCPR deals with a topic, such as refuge areas or rainwater harvesting. Returns lines of UDCPR that contain all the given words, with their chapter; a regulation's own heading first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| words | string | yes | — |
Use this when the town or planning authority of a plot is unclear or spelt differently. Returns Maharashtra towns and authorities with their kind and class; every one when no query is given.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | — |
Use this when a plot's shape is given as measurements rather than as one area: side lengths with the angles at the corners, or with diagonals, as on a hand-drawn sketch, a measurement sheet or a survey; or the corners themselves. Works out the exact corners, checks every measurement that is given twice (closing side, angle sum, spare diagonals, stated area) and reports any misfit, and returns the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sides | array | yes | every side in order round the plot, either direction; at least one is a road |
| unit | string | no | unit of every length and road width; default m |
| angles | array | no | interior angle in degrees at each corner; corner i is where side i begins |
| diagonals | array | no | corner-to-corner distances; a plot of n sides needs n - 3, e.g. from corner 1 to each corner it does not touch |
| right_angles | boolean | no | true when every corner of a four-sided plot is square |
| polygon | array | no | the corners [x, y] instead of lengths and angles, one per side |
| stated_area | number | no | the area on the 7/12 or measurement sheet, in m2 (or sq ft with unit ft), to check against |
| town | string | no | with use: also run the feasibility |
| use | string | no | — |
| zone | string | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Citiwise or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.4.0.
1.4.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Citiwise can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.