US Places, Then MCP Server

What this does

US Places, Then exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server declares the following environment variables. Set only the ones the maker requires for your setup; this listing does not flag any of them as required:

US_PLACES_OVERPASS_URL
US_PLACES_PLSS_URL
US_PLACES_GNIS_URL
US_PLACES_GNIS_ARCHIVE_URL
US_PLACES_TNM_URL
US_PLACES_DATAVERSE_URL
US_PLACES_CACHE_DIR
US_PLACES_TIMEOUT
US_PLACES_CONTACT

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install US Places, Then?

Run the Claude Code command in the install section to add US Places, Then to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with US Places, Then?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to US Places, Then as well.

Does US Places, Then need an API key?

This listing does not flag an API key as required. The server can use these environment variables: US_PLACES_OVERPASS_URL, US_PLACES_PLSS_URL, US_PLACES_GNIS_URL, US_PLACES_GNIS_ARCHIVE_URL, US_PLACES_TNM_URL, US_PLACES_DATAVERSE_URL, US_PLACES_CACHE_DIR, US_PLACES_TIMEOUT, US_PLACES_CONTACT; the maker's docs say which of them your setup needs. They go in the env block of your MCP config.