urbankitstudio/mcp-atlas

Query the parcel ArcGIS REST endpoints of 499 counties across 51 US states (50 states plus DC), 497 endpoints total, for owner, APN and address lookup via the Model Context Protocol (MCP).
An MCP server that gives AI assistants direct access to UrbanKit Studio's atlas of manually verified county parcel GIS services. Ask Claude or Cursor to find the ArcGIS REST endpoint for any covered county, get the exact owner-search query URL, and look up parcel data — without needing to know anything about ArcGIS REST API conventions.
Coverage: 499 counties across 51 US states (50 states plus DC), 497 endpoints, 497 of them live (atlas 0.6.40). 470 of the counties have an endpoint; for the other 29 the atlas records why not (see "A county we cannot serve" below).
## Quick start
### Claude Desktop
Add to ~/Library/Application Support/Claude/claudedesktopconfig.json (macOS) or %APPDATA%\Claude\claudedesktopconfig.json (Windows):
json
"mcpServers": {
"mcp-atlas": {
"command": "npx",
"args": ["-y", "@urbankitstudio/mcp-atlas"]
### Cursor
Add to .cursor/mcp.json in your project root (or ~/.cursor/mcp.json globally):
json
"mcpServers": {
"mcp-atlas": {
"command": "npx",
"args": ["-y", "@urbankitstudio/mcp-atlas"]
### Install globally (optional)
sh
npm install -g @urbankitstudio/mcp-atlas
Then use mcp-atlas as the command instead of npx -y @urbankitstudio/mcp-atlas.
## Tools
The first four tools are one county pipeline, and what separates them is how
precisely you can already name the county. The fifth, getcitydatasets, is
separate: it answers about a city, not a county.
| You have | Use | You get |
| A state, or nothing | listcounties | Which counties are covered, and whether owner search works there. No URLs. |
| A vague, misspelled or FIPS reference | findcounty | Every county that reference matches, named, each with its record |
| An exact state and county | getparcelendpoint | That one county's endpoint URL, layer, fields and sample query |
| A county and an owner's name | buildownerquery | A runnable URL that searches for that name |
| A city, and optionally a street | getcitydatasets | That city's code-violation, building-permit and zoning-case datasets, each with a runnable query URL |
findcounty and getparcelendpoint return the same per-county record. They
differ in how you address the county: findcounty accepts an uncertain
reference and may come back with several candidates, getparcelendpoint
takes an exact pair and answers about one. If you already know the county, skip
findcounty.
This server never executes a query and returns no parcel records. It tells you
the URL to fetch; fetching it is yours to do.
### A county we cannot serve
findcounty, getparcelendpoint and buildownerquery give one answer for
a county with no endpoint to hand back, the same text the hosted UrbanKit MCP
server, its REST API and the uks CLI give. It comes from
coverageAnswer() in @urbankitstudio/atlas 0.6.38:
The atlas has no record (a misspelling lands here too): "This county is not
in the UrbanKit atlas", with a prompt to check the spelling first.
The atlas records the county and it publishes nothing we can serve (Shelby
TN, whose terms bar public display; Columbia PA, whose layer has parcel numbers