Country State City vs Zippopotam

In-depth architectural comparison of the Country State City and Zippopotam MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Country State City when:

• You need dedicated capabilities in the Location Services domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: list_countries, get_states, get_cities.

Explore Country State City Details

Choose Zippopotam when:

• You need dedicated capabilities in the Location Services domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: lookup_zipcode, lookup_city.

Explore Zippopotam Details

Feature & Specification Comparison

Specification	Country State City Location Services	Zippopotam Location Services
Summary	CountryStateCity MCP — wraps CountryStateCity API (api.countrystatecity.in/v1)	Zippopotam MCP — wraps Zippopotam.us ZIP/postal code API (free, no auth)
Category & Scope	Location Services	Location Services
Quality signal

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "country-state-city": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-country-state-city"
      ]
    }
  }
}

{
  "mcpServers": {
    "zippopotam": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-zippopotam"
      ]
    }
  }
}

Related MCP Server Comparisons