Skip to main content
For AI assistants

Manage your gear and trips from your AI assistant

TrailPack now speaks MCP (Model Context Protocol). Connect it to Claude Desktop, Claude on the web, or any MCP-capable assistant and plan trips by just talking to it — your gear list and trips stay in sync with your account. The assistant also knows the terrain — marked trails, huts, springs, avalanche ratings — so it can suggest a route and what to take on it.

What you can do

Your gear

List, search, add, edit or remove items in your gear list — including weights and notes. Fuzzy search finds items even with typos or without diacritics.

Your trips

Create trips, set dates, and assign gear with a packing status (taking, packed, considering). Apply a template, duplicate a trip, or ask for a weight summary.

Routes and terrain

New

Ask it to plan a route and it works out the distance, ascent, difficulty and what you will pass — huts, springs, via ferratas. Real trail data, not guesswork.

For example, just ask:

  • “Create a trip to the Tatras next weekend and add my sleeping bag and tent.”
  • “Plan me a route from Adamekhütte to Hoher Dachstein and tell me how long it takes.”
  • “What’s the total weight of gear I’m taking on my Alps trip?”
  • “Are there any springs along this route? What’s the longest stretch without water?”
  • “Add a 300 g headlamp to my gear under Lighting.”
  • “What’s the avalanche risk in the Dachstein this weekend?”

Getting the most out of it

Your assistant handles the simple commands above just fine. But you get the most out of it when you describe the whole trip instead of individual tasks — it works out the rest itself.

Try something like this:

“I want to walk the Dachstein traverse in mid-September, two days, sleeping at a hut. Plan the route, tell me what I will pass, and put together the gear — including anything the terrain calls for.”

The assistant plans the route, sees it crosses a glacier and reaches T4 difficulty, and adds crampons and a helmet on its own — then tells you the pack weight and where the water is.

Show the assistant’s answer

Day 1 · Hunerkogel → Hoher Dachstein → Simonyhütte

Cable car up, then the glacier route below the Dirndln faces, the summit via the Randkluft via ferrata, and down past the Eisjoch to the hut. 8.5 km, +686/−1116 m, 4.6 h of pure walking — with the glacier, the ferrata and the summit, reckon on 7–8 h. Max SAC T5, ferrata B, steepest section 65°.

View the route in the planner

Day 2 · Simonyhütte → Krippenstein → Obertraun

Down to Wiesberghaus, then across the karst plateau to Gjaid Alm, up Krippenstein and down by cable car. 10.6 km, +647/−790 m, 4.3 h, max SAC T3.

View the route in the planner

What the terrain called for

  • Crampons and an ice axe — in mid-September the glacier is bare blue ice with open crevasses, not firn.
  • Helmet and via ferrata set — the Randkluft ferrata, plus rockfall in the gullies.
  • Rope flagged as “considering” — take it if you are two or more, dead weight solo.
  • Sleeping bag, mat and stove dropped — the hut cooks, so only a liner stays.
  • Water for the whole of day two — there is not a drop on the karst plateau.

Final pack: 8.9 kg, heaviest category mountain gear at 36 %. Both days came with a link to the route in the planner.

A real answer, shortened. Times, opening hours and hut bookings are the assistant’s own knowledge — always check them yourself.

Give it context, not a list

Trip type, accommodation, difficulty, season. Once it knows you are sleeping in a hotel, it leaves out the sleeping bag, mat and stove on its own. For a bivouac it adds them instead.

Ask about the terrain

Ask what the route is like before you pack. Ascent, difficulty, whether it crosses a glacier — the assistant reads it from real map data.

Let it work with statuses

Ask it to mark weather- or mood-dependent items as “considering” rather than “taking”. In the app you will then see your pack weight split between what is certain and what is still optional.

Ask about weight

Try “how much does this weigh?” or “what can I leave at home to save a kilo?”. The assistant knows the weights of your items and how they break down by category and bag.

Avalanches and the season

For winter trips ask about the avalanche rating. The assistant reads the EAWS bulletin for the regions your route crosses — during the season only, and it is not a substitute for reading the bulletin yourself.

Refine it by talking

A finished trip is not final. “Add poles and a headlamp” or “I am not taking the tent after all” — every change lands in the app straight away.

Split things into bags

Say “put whatever I do not need on the trail in the car” and the assistant creates the bags and sorts your items into them. You then see the weight for each one separately.

A note on shared trips

The assistant also sees trips shared with you and respects your role — where you are only allowed to pack, it will not overwrite the gear.

How to connect

Connecting takes about a minute. You sign in with the same Google or Apple account you already use here — there are no API keys to generate or paste.

  1. 1

    Open your assistant’s connector settings

    In Claude Desktop or Claude on the web, go to Settings → Connectors (or “Add MCP server”). Other MCP clients have a similar option.

  2. 2

    Add TrailPack as a server

    Paste this server URL when the client asks for it:

    Server URL
    https://trailpack.eu/mcp
  3. 3

    Sign in and approve

    A TrailPack window opens. Sign in with Google or Apple and confirm access. That’s it — your assistant can now work with your gear and trips.

Safe by design

  • No passwords or API keys to copy — connection uses secure OAuth sign-in with your existing account.
  • The assistant only sees your own gear and trips, never other users’ data.
  • You can revoke access anytime by signing out of the connector in your AI assistant.

Don't have an account yet?

You’ll need a TrailPack account to connect. It’s free and takes a moment.

Get started