Plenty of people already plan trips by talking to an AI assistant. The Anemos connector means you don't have to copy the result anywhere: your assistant can search Anemos's recommendations from real locals while you plan, and save the finished itinerary directly to your Anemos account, handing you a link to open it.
The connector URL
This is the address you paste into your assistant:
https://anemos.travel/mcp
It speaks the Model Context Protocol (MCP) over HTTPS, and authenticates with OAuth 2.1 — you sign in to Anemos in your own browser, and the assistant never sees your password.
What the assistant can do
| Tool | What it does | Access |
|---|---|---|
search_local_recommendations |
Looks up Anemos's published recommendations from named locals for a city, with each local's own tip. | Read-only. Published content, not your personal data. |
list_trips |
Lists the trips saved in your account, so the assistant can refer to one. | Read-only. Your saved trips. |
create_trip |
Saves a new itinerary to your account and returns a link to open it. Anemos resolves map coordinates for the places itself. | Adds a trip. It never edits or deletes an existing trip, and publishes nothing publicly. |
Adding it to ChatGPT
- Open Settings › Connectors and turn on Developer mode (available on Plus, Pro, Business, Enterprise, and Edu on the web).
- Choose Create / Add custom connector.
- Paste
https://anemos.travel/mcpas the MCP server URL. - Sign in to Anemos when prompted and approve the connection.
Adding it to Claude
- Open Customize › Connectors.
- Choose Add custom connector.
- Paste
https://anemos.travel/mcpas the remote MCP server URL. - Sign in to Anemos when prompted and approve the connection.
On Claude Team and Enterprise plans an organization owner adds the connector under Organization settings first; members then connect their own Anemos account to it.
What gets shared, and when
- Nothing is shared until you approve the connection, and then only when the assistant actually calls one of the three tools above.
- When it does, the relevant trip data travels between Anemos and your assistant's provider (OpenAI or Anthropic), where it is handled under their privacy policy and your settings with them.
- Anemos stores the access grant itself — which app you connected, the permissions you granted, and when it was last used. Access and refresh tokens are stored hashed, never in readable form.
- The connector cannot read your Anemos planning conversations, your account password, or your payment details.
The full picture is in our Privacy Policy.
Revoking access
In Anemos, open Settings › Connected apps, find the assistant, and choose Revoke. This invalidates its tokens immediately — the next tool call it attempts will fail. Removing the connector on the assistant's side as well keeps things tidy, but revoking in Anemos is what actually cuts off access.
Troubleshooting
The assistant says it can't reach Anemos
Check that the URL is exactly https://anemos.travel/mcp — no
trailing slash, no /api/v1 prefix.
It asks me to sign in again
Access tokens are short-lived and refresh automatically. Being asked to approve again usually means the grant was revoked — check Settings › Connected apps.
Some places didn't get saved
Anemos only saves a place it can put on a map. Anything it can't locate is named back to the assistant rather than dropped silently, so ask it which ones, then add them by hand in the app.
Support
Questions, bug reports, or trouble connecting: [email protected].