Cityparity — Cost MCP Server

If you already use Cityparity — Cost, the cityparity — cost mcp server is the piece that lets your assistant work with it directly. Cost-of-living & quality-of-life comparison: take-home pay, equivalent salary, safety-net deltas.

What the server does

Cost-of-living and quality-of-life comparison tools that AI agents can call. Point an agent at two cities and it returns take-home pay, a full cost breakdown, the equivalent salary you'd need in the target city, and the non-cash deltas people actually move for: vacation, parental leave, universal healthcare.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• compare_cities — Full scenario comparison between two cities: take-home, cost breakdown, equivalent target salary, lifestyle deltas, quality score
• list_cities — Discover supported city slugs, grouped by country
• get_city_summary — One-city profile: tax shape, headline costs, safety-net values
• rank_cities — Top N cities by composite quality score, with custom weights and region/country filters
• get_safety_net — Parental leave, universal-healthcare flag, vacation, public holidays for 1 to 20 cities
• get_inbound_tax_regime — Inbound-worker regimes: Italy impatriati, Portugal IFICI, Belgium expat, Poland B2B ryczałt, Greece inbound
• Cursor — The Cursor tool exposed by this server

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Credentials and setup notes

Configuration is passed through the environment: CITYPARITY_MCP_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Cityparity — Cost's toolset — compare_cities, list_cities, get_city_summary and 4 more — is a fair guide to whether it matches your workflow. It is maintained by com.cityparity; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.