Your AI Can Now Build the Trip, Not Just Describe It

Ask an assistant to plan five days in Kyoto and you'll get something genuinely good. Then you close the tab. Plany changes what happens next.

There's a moment in AI trip planning that everyone has had and nobody talks about. You describe the trip you want. The assistant thinks for a few seconds and produces a plan that is, honestly, quite good — a sensible route through the city, a temple in the morning light, a soba place someone who lives there would actually recommend. You read it. You think, yes, that's the trip.

And then it's just text on a screen. To make it real you copy it into a notes app, or a spreadsheet, or you retype the whole thing into a calendar one entry at a time. Somewhere in that transfer the plan stops being a plan and becomes a chore. Most people never finish. The good itinerary quietly evaporates.

The problem isn't the quality of the planning. It's that the assistant had nowhere to put it.

Without a connection: the assistant writes an itinerary, you read it, and the conversation ends — the itinerary ends with it.

With Plany connected: the assistant builds the itinerary inside your calendar. Days laid out, places pinned, times set. It's on your phone before you've finished talking — and it's still there next week when the plan changes.

What changes when the AI can write?

Plany runs an MCP server — a standard way for AI assistants to use an app's real features rather than just talk about them. Connect your Plany account to Claude or ChatGPT once, and the assistant stops handing you plans and starts making them.

The difference sounds small and isn't. When you say "plan me five days in Kyoto, two temples a day, and don't make me walk more than twenty minutes between things", the assistant doesn't compose an answer. It creates the trip, lays out the five days, fills each one with actual named venues, and puts it in your hands as a finished itinerary you can open, edit, and share. The output isn't a description of a trip. It's the trip.

What can the assistant actually do?

More than most people expect, and all of it inside your own trip rather than in a chat window.

It builds the shape of the trip. Creates the trip itself, sets the dates, lays out the days, and titles them so "Day 3" becomes "Arashiyama and the west side."

It adds real places, not descriptions of places. Not "a well-reviewed ramen spot near the station" — the actual restaurant, pinned to its actual location, with an address you can tap into a map when you're standing on the street at 8pm. This matters more than it sounds like it should. A plan made of adjectives falls apart the moment you're hungry.

It checks whether the day is physically possible. The assistant can measure the real travel time between the stops it just planned. If it's put breakfast in one district and a 10am booking forty minutes away, it can see that and fix it before you do.

It reads the trip back and revises it. This is the part that only works when the itinerary persists. Come back a week later and say "the flight moved, push everything two days" or "swap Tuesday's dinner for somewhere quieter" — the assistant opens what already exists, changes precisely that, and leaves the rest alone. It isn't regenerating a plan from scratch. It's editing yours.

It picks up the places you'd already saved. The restaurant from a friend's Instagram, the viewpoint from a TikTok you watched three months ago. Those saved ideas are available to the assistant, so the trip it builds includes the things you'd found yourself and forgotten about.

Why does this work in Plany and not in a notes app?

Because of what a trip is here.

In most travel tools, an itinerary is a document — paragraphs, bullet points, a block of text with times in it. An AI writing into a document produces more text. That's all it can produce, because that's all the container will hold.

Plany was built the other way round. A trip is a calendar, and every item on it is a real thing with a type: a flight is a flight, a hotel is a hotel, a dinner reservation is a dinner reservation. Each one is anchored to a genuine, resolved location rather than a name someone typed. That structure is what a person sees as a clean, readable day plan — and it's the same structure an AI can write into precisely.

So the assistant isn't drafting prose that happens to look like an itinerary. It's placing typed events on specific days at specific coordinates. That's why the result behaves like a trip you made yourself: you can drag it around, share it, export it, hand it to a travel companion, and open it offline in a foreign city.

Is it safe to let an AI into my trip?

You decide, explicitly, once. Connecting Plany to an assistant means signing in to your own Plany account and granting access — the same way you'd connect any app to another. Nothing happens before that, and you can disconnect at any time from your Plany settings, which immediately ends the assistant's access.

Within that connection, the boundaries are firm. An assistant can only change trips you own. A trip someone has shared with you stays read-only — an AI acting on your behalf cannot rewrite your friend's itinerary. Every action taken through the connection is recorded, so there's an actual record of what was done and when, rather than changes appearing in your calendar from nowhere.

The technical detail, for anyone who wants it: Plany's MCP server lives at api.plany.ae/v1/mcp/rpc and uses OAuth with scoped permissions. It's available on Plany Pro.

Which assistants does it work with?

Claude and ChatGPT today, and any assistant that speaks MCP as the standard spreads. That last part is deliberate. We didn't want to build one more chatbot inside one more app and ask you to learn it. You already have an assistant you like and know how to talk to. Plany's job is to be the place its work actually lands.

Setup takes about a minute and is documented on the Plany features page.

From describing trips to keeping them

AI got good at travel planning faster than travel apps got ready for it. For a couple of years now the assistants have been able to plan a better week in Kyoto than most guidebooks, and all of it has been landing in chat windows and getting lost.

The interesting shift isn't AI that plans better. It's AI that plans somewhere the plan survives — where the trip you built on a Tuesday night is still there in March, on your phone, when the flight gets delayed and the whole thing needs to move two days to the right.

That's the part we built.