Nomads.com MCP server for AI apps

What your AI apps can do with Nomads.com

Compare cities by cost, internet, weather and safety
Manage your trips, favorites and meetups when signed in

Nomads.com MCP tools

14 tools, listed by Toolstile from the server itself on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.

Tool	What it does	Suggested rule
`search_cities`	Search Nomads.com for the best cities to live and work remotely. Filters: budget, region, country, internet speed, safety, temperature. Returns at most 100 cities sorted by overall score. Each city includes costs, internet, weather, air quality, safety/cleanliness/healthcare/fun …	Allow (read-only)
`list_meetups`	Upcoming Nomads.com meetups: where and when nomads meet in person, and how many people are going. Filter by city slug, country or how far ahead to look. Attendance is a count only; who attends is private.	Allow (read-only)
`create_meetup`	Host a Nomads.com meetup as the member: it is posted in the community chat, members in that city then get notified, and at 2 RSVPs it is also shared in the country channel and on X. Authenticated as the member (signed in through the connector with OAuth or an Authorization …	Allow or Require approval (changes data)
`edit_meetup`	Change a Nomads.com meetup the member organized: date, time, type, title, description, venue or address. Fields left out keep their current value. The change is posted in the community chat. Once 2+ people RSVP'd, the date and time can no longer change. Call without meetup_id to …	Allow or Require approval (changes data)
`cancel_meetup`	Cancel a Nomads.com meetup the member organized. The cancel is posted in the community chat and everyone who RSVP'd gets a notification. It cannot be undone. Call without meetup_id to get the member's upcoming meetups with their ids. Authenticated as the member, like …	Require approval (may delete or overwrite)
`get_country`	Get one country by its slug, e.g. portugal or united-kingdom: its Nomads.com page, its short animated thumbnail video (mp4, when there is one) and its top 10 cities by overall score, each with their own animated thumbnail.	Allow (read-only)
`get_city`	Get the curated data for one city by its slug (from search_cities), e.g. lisbon-portugal.	Allow (read-only)
`get_favorites`	Get a Nomads.com member's own favorite cities and countries (the places they hearted: places they want to go or come back to). Authenticated as the member: signed in through the connector (OAuth sign-in or an Authorization header) if set up, otherwise pass the member's username …	Allow (read-only)
`add_favorite`	Save a city or country to the member's Nomads.com favorites (the heart on the site). Authenticated as the member, like get_favorites.	Allow or Require approval (changes data)
`remove_favorite`	Remove a city or country from the member's Nomads.com favorites. Authenticated as the member, like get_favorites.	Require approval (may delete or overwrite)
`get_trips`	Get a Nomads.com member's own trip history (past and upcoming stays: city, country, dates), newest first, 200 by default; use from_date/to_date for a period and limit for more. Authenticated as the member: signed in through the connector (OAuth sign-in or an Authorization …	Allow (read-only)
`add_trip`	Add a trip to a Nomads.com member's own history: a stay in one place with a start and end date. Authenticated as the member: signed in through the connector (OAuth sign-in or an Authorization header) if set up, otherwise pass the member's username and their personal key from …	Allow or Require approval (changes data)
`remove_trip`	Remove one trip from a Nomads.com member's own history, e.g. a duplicate or a superseded entry. Authenticated as the member (signed in through the connector with OAuth or an Authorization header, or username + personal key from https://nomads.com/settings). Needs the trip_id …	Require approval (may delete or overwrite)
`edit_trip`	Change the dates and/or the place of one trip in a Nomads.com member's own history, e.g. a stay that got longer or a wrong city. Authenticated as the member (signed in through the connector with OAuth or an Authorization header, or username + personal key from …	Allow or Require approval (changes data)

Suggested access for each AI app

6 tools marked read-only (search_cities, list_meetups, get_country, get_city, get_favorites, get_trips). These are usually safe to allow.
5 tools that change data without deleting it (create_meetup, edit_meetup, add_favorite, add_trip, edit_trip). Allow them for apps you supervise, or require approval.
3 tools that may delete or overwrite data (cancel_meetup, remove_favorite, remove_trip). Require approval, or block them for apps that don't need them.

These are hints the server reports about its own tools, not guarantees.

Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.

Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.

Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.

Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same Nomads.com connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.

How it works with Toolstile

Connect once. Add Nomads.com to a workspace (no sign-in or browser sign-in or access token). Toolstile keeps the credential, so no agent config holds it.
Choose access per app. Give Claude Code every Nomads.com tool, give Cursor only the read tools, or keep Nomads.com away from an app entirely.
Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
Review activity. See which app called which tool and when, so you can tighten access with evidence.

Add the Nomads.com MCP server to an AI app

Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:

Shell

claude mcp add --transport http toolstile 'https://mcp.toolstile.com/mcp'

Then connect Nomads.com in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.

To connect directly instead, add the Nomads.com endpoint to each app separately. In Claude Code:

Shell

claude mcp add --transport http nomads 'https://nomads.com/mcp'

In Cursor's mcp.json:

JSON

{
  "mcpServers": {
    "nomads": {
      "url": "https://nomads.com/mcp"
    }
  }
}

Some servers accept only clients they have approved, or need a token header. Check the Nomads.com MCP documentation for what your client needs.

Before you connect

City research needs no sign-in. Member features require a Nomads.com account. Results are capped and rate limited; bulk data access is not supported.

Choose browser sign-in for member features, or enter username:key from nomads.com/settings as the access token. No sign-in only supports public tools. City-data limits are shared by the upstream IP address.

Server details

Detail	Value
Publisher	Nomads.com
Endpoint	`https://nomads.com/mcp`
Authentication	No sign-in or browser sign-in or access token
Categories	Marketing & research
Tool list	14 tools, observed 29 October 2026 (discovery)

Nomads.com MCP documentation

Nomads.com MCP server for Claude, Codex and Cursor