US Places, Then MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add us-places-mcp -- uvx us-places-mcp

{
  "mcpServers": {
    "us-places-mcp": {
      "args": [
        "us-places-mcp"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.us-places-mcp]
command = "uvx"
args = ["us-places-mcp"]

{
  "mcpServers": {
    "us-places-mcp": {
      "args": [
        "us-places-mcp"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "us-places-mcp": {
      "args": [
        "us-places-mcp"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: US_PLACES_OVERPASS_URL (OpenHistoricalMap's Overpass endpoint.), US_PLACES_PLSS_URL (BLM's national PLSS (CadNSDI) map service.), US_PLACES_GNIS_URL (USGS's GNIS map service (The National Map).), US_PLACES_GNIS_ARCHIVE_URL (Where USGS keeps the August 2021 GNIS state files.), US_PLACES_TNM_URL (The National Map's TNM Access products API.), US_PLACES_DATAVERSE_URL (Harvard Dataverse, which holds the US post offices dataset.), US_PLACES_CACHE_DIR (Directory for the on-disk response cache and the downloaded datasets.), US_PLACES_TIMEOUT (HTTP timeout in seconds.), US_PLACES_CONTACT (An email address or URL appended to the User-Agent, so the services can reach whoever runs the server.). The author declared them in the registry entry; get the values from the project itself.