
Mcp Atlas
io.github.urbankitstudiov0.2.22Updated Oct 10, 2026
Owner and APN lookup across 286 US counties (297 ArcGIS endpoints). No API key needed.
Overview
Looks up US county parcel GIS endpoints and builds ArcGIS owner-search query URLs for 286 counties.
- What it does
- Provides four tools over an embedded atlas of 286 US counties and 297 ArcGIS REST endpoints. list_counties shows which counties are covered and whether owner search works there; find_county fuzzy-matches a partial name, phrase or FIPS code; get_parcel_endpoint returns one county's endpoint URL, layer, searchable fields and sample query; build_owner_query returns a runnable URL that searches a county's owner/taxpayer field for a partial name. It never executes a query or returns parcel records — it only tells you which URL to fetch.
- When to use it
- Useful when you need to locate the right county parcel GIS service or construct an owner or parcel-number search URL without knowing ArcGIS REST conventions. Suited to property due diligence, ownership research and parcel data work where you already know or can name a US county.
- Requirements
- Runs locally over stdio, typically via npx @urbankitstudio/mcp-atlas or a global npm install, so Node.js and npm are needed. No API key, account, environment variable or header is declared. Atlas data is embedded in the package, so no network call is made at startup; fetching the returned query URLs requires network access.
Installation
In SourceWeft
- Open Mcp Atlas in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@urbankitstudio/mcp-atlas
Query the parcel ArcGIS REST endpoints of 286 counties across 51 US states (50 states plus DC), 297 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: 286 counties across 51 US states (50 states plus DC), 297 endpoints, 296 of them live (atlas 0.6.25).
Quick start
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
Cursor
Add to .cursor/mcp.json in your project root (or ~/.cursor/mcp.json globally):
Install globally (optional)
Then use mcp-atlas as the command instead of npx -y @urbankitstudio/mcp-atlas.
Tools
The four tools are one pipeline, and what separates them is how precisely you can already name the county:
find_county and get_parcel_endpoint return the same per-county record. They
differ in how you address the county: find_county accepts an uncertain
reference and may come back with several candidates, get_parcel_endpoint
takes an exact pair and answers about one. If you already know the county, skip
find_county.
This server never executes a query and returns no parcel records. It tells you the URL to fetch; fetching it is yours to do.
list_counties
Browse coverage. Answers "is this county covered?" and "what can I search there?" — one line per county, with no endpoint URLs or field names.
Example prompt: "List all covered counties in Illinois"
Example output:
What each Coverage label promises:
find_county
Resolves a reference you cannot state exactly. Fuzzy-matches a partial or misspelled name, a "County State" phrase, or a 5-digit FIPS code against every covered county, and names each county it matched so an ambiguous reference comes back as a list to choose from. Each match carries that county's record: endpoint URLs, searchable field names, owner field, sample query, license.
Example prompt: "Find the parcel endpoint for Kane County Illinois"
get_parcel_endpoint
The default lookup once the county is known. Returns the full ArcGIS REST URL,
layer index, searchable fields, owner field (or why no owner query is offered),
the county's Scope: predicate when the layer is shared statewide or
regionally, a generic sample ?where=…&f=json query and the UrbanKit deep-link
for one county. For a named owner, use
build_owner_query rather than editing the sample query by hand.
Example prompt: "Give me the ArcGIS REST endpoint for Cook County Illinois"
build_owner_query
The only tool that searches for a named owner. Fills a person or company name
into the county's verified owner/taxpayer field as
UPPER(field) LIKE UPPER('%NAME%'), a case-insensitive partial match, and
returns a URL you can fetch or open. On a shared statewide or regional layer
(Connecticut's regional composites, for example) the county's scope predicate
is ANDed in front, as
(scope) AND UPPER(field) LIKE …, so only that county's rows come back.
An endpoint is refused, with the reason, rather than handed a query that finds nothing or hangs:
- a reviewed record says the county publishes no usable owner name;
- the layer serves no attribute search at all (query it by location instead);
- the owner column is not searchable by name (use a parcel-id or location query).
Example prompt: "Build an ArcGIS query for properties owned by 'Smith' in Kane County IL"
Example output:
Example conversation
User: I'm doing due diligence on properties in Kane County, Illinois. Can you find all parcels owned by "Blackstone"?
Claude (using mcp-atlas):
- Calls
get_parcel_endpoint→ gets thegistech.countyofkane.orgURL and confirms the owner field isTaxName- Calls
build_owner_querywithowner_name=Blackstone→ returns a ready fetch URL- Optionally fetches the URL and formats the parcel results
Atlas coverage
The atlas is maintained by UrbanKit Studio. All endpoints are manually verified. Counties with an owner/taxpayer field support full name-based lookups; PIN-only counties support APN/parcel-number queries.
Full coverage map: https://urbankitstudio.com/parcel-atlas
Data
Atlas data is embedded in the package (no network calls at startup). The underlying @urbankitstudio/atlas SDK is also published separately for programmatic use.
What Socket flags, and how much of it is ours
Socket's supply-chain scanner rates this package in the mid-70s. Clicking through shows a long alert list. Each alert, checked rather than waved away:
Vulnerability and license both come back at 100, quality at 99. The number the badge shows is the supply-chain sub-score, and its single largest deduction is download count, a popularity measure wearing a security badge's clothes. Judge the list above, not the digit.
The four access alerts are what let the server read its own config and talk to a client over stdio, nothing more. It still never executes a query or returns a parcel record.
License
MIT — © 2026 UrbanKit Studio
Source: README.md at commit 7be3e34
Tools
0Version history
1- v0.2.22LatestOct 10, 2026
