Stockholm Archipelago Trail
Server Details
Trail stages, ferry piers, timetabled day trips and A→B routes for the Stockholm Archipelago Trail.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Score is being calculated.
Available Tools
10 toolscheck_day_tripRead-onlyInspect
Same data as day_trip but renders NO card. Use this when you need to check or compare day trips across dates, departure hubs or stages before recommending one, or for follow-up questions where no new card is wanted. Same arguments and response as day_trip (section, date, hub, targetKm, direction, towards). Do not use for the final recommendation shown to the user (use day_trip) — call day_trip once for the trip you recommend.
| Name | Required | Description | Default |
|---|---|---|---|
| hub | No | Optional preferred departure hub slug from check_day_trip/day_trip responses, e.g. 'stromkajen'. Omit to let the planner pick the best. | |
| date | No | Travel date, YYYYMMDD (Europe/Stockholm), e.g. 20260905. Defaults to today. | |
| lang | No | Language of the user's message: 'sv' when the user writes in Swedish, otherwise 'en'. Always pass it — labels, dates and the card are rendered in this language. | |
| section | Yes | Section reference: satId, slug or uid, e.g. 'uto'. | |
| towards | No | Optional named place on the island (beach, viewpoint, café) to steer the walk towards, as shown by search/fetch — e.g. 'Stora Sandvik'. | |
| targetKm | No | Desired walking distance in km, 1–60, e.g. 9. Pass when the user asks for a shorter or longer walk than the full stage (e.g. "about 9 km"). Omit for the full stage. | |
| direction | No | Optional compass direction to steer a shorter walk towards: one of N, NE, E, SE, S, SW, W, NW — e.g. 'NE' to walk towards the north-east part of the island. |
Output Schema
| Name | Required | Description |
|---|---|---|
| hub | No | Departure ferry hub. |
| date | No | YYYYMMDD. |
| kind | Yes | "day-trip" | "no-day-trip". |
| walk | No | Present when targetKm was passed: the actual walk that was built. |
| title | No | |
| reason | No | Why no trip/walk could be built. |
| return | No | Ferry island → hub. |
| section | No | |
| outbound | No | Ferry hub → island. Times "HH:MM" (Europe/Stockholm). |
| permalink | No | |
| islandWalk | No | |
| boatsPerDay | No | |
| feasibility | No | "comfortable" | "tight". |
| variantNote | No | Present when a requested targetKm walk could not be built: the full stage is shown instead. Tell the user this. |
| nextDateWithTrip | No | Only with kind "no-day-trip": the next date (YYYYMMDD) within the timetable that does have a day trip, when one was found. |
| suggestedFollowUps | No | Up to three short next steps, in English (e.g. "Make the walk shorter"). Offer these to the user as quick follow-up options at the end of your reply. |
| timeOnIslandMinutes | No |
day_tripRead-onlyInspect
Plan a ready round-trip day trip to one trail section (island) of the Stockholm Archipelago Trail on a given date. Returns the best ferry hub to depart from, outbound and return ferry times, the walking time around the island and how many ferries run that day. Use this when the user wants a day-trip suggestion to a single island. Section takes the same identifiers as fetch (sat:section:…, slug or uid). Pass targetKm when the user asks for a shorter or longer walk than the full stage; the response then describes that walk and permalink opens it in the planner. Do not use for a one-way trip between two islands (use plan_route), for probing several dates or hubs before recommending one (use check_day_trip), or for multi-day trips (use multi_day). ALWAYS follow this call with show_section_map for the same section, date and targetKm so the user also sees the walk on the map — the map is the main deliverable, not optional. IMPORTANT: every call to this tool renders a card in the conversation. Call it at most ONCE per answer, for the single option you recommend. Never use it to compare or probe alternatives. The card already shows ferry times, piers and walking times — do not restate them in your reply; add only advice, caveats and next steps.
| Name | Required | Description | Default |
|---|---|---|---|
| hub | No | Optional preferred departure hub slug from check_day_trip/day_trip responses, e.g. 'stromkajen'. Omit to let the planner pick the best. | |
| date | No | Travel date, YYYYMMDD (Europe/Stockholm), e.g. 20260905. Defaults to today. | |
| lang | No | Language of the user's message: 'sv' when the user writes in Swedish, otherwise 'en'. Always pass it — labels, dates and the card are rendered in this language. | |
| section | Yes | Section reference: satId, slug or uid, e.g. 'uto'. | |
| towards | No | Optional named place on the island (beach, viewpoint, café) to steer the walk towards, as shown by search/fetch — e.g. 'Stora Sandvik'. | |
| targetKm | No | Desired walking distance in km, 1–60, e.g. 9. Pass when the user asks for a shorter or longer walk than the full stage (e.g. "about 9 km"). Omit for the full stage. | |
| direction | No | Optional compass direction to steer a shorter walk towards: one of N, NE, E, SE, S, SW, W, NW — e.g. 'NE' to walk towards the north-east part of the island. |
Output Schema
| Name | Required | Description |
|---|---|---|
| hub | No | Departure ferry hub. |
| date | No | YYYYMMDD. |
| kind | Yes | "day-trip" | "no-day-trip". |
| walk | No | Present when targetKm was passed: the actual walk that was built. |
| title | No | |
| reason | No | Why no trip/walk could be built. |
| return | No | Ferry island → hub. |
| section | No | |
| outbound | No | Ferry hub → island. Times "HH:MM" (Europe/Stockholm). |
| permalink | No | |
| islandWalk | No | |
| boatsPerDay | No | |
| feasibility | No | "comfortable" | "tight". |
| variantNote | No | Present when a requested targetKm walk could not be built: the full stage is shown instead. Tell the user this. |
| nextDateWithTrip | No | Only with kind "no-day-trip": the next date (YYYYMMDD) within the timetable that does have a day trip, when one was found. |
| suggestedFollowUps | No | Up to three short next steps, in English (e.g. "Make the walk shorter"). Offer these to the user as quick follow-up options at the end of your reply. |
| timeOnIslandMinutes | No |
fetchRead-onlyInspect
Fetch the full machine-readable record (JSON-LD) for one object by identifier. Accepts sat-ids (sat:section:…, sat:pier:…, sat:vessel:…, sat:poi:…, sat:trail:…, sat:report:…), section slugs, legacy OSM ids (osm:node:…), Wikidata QIDs (wikidata:Q…), GTFS stop ids (gtfs:…) and Swedish AED-registry ids (shr:…). Deleted objects return a tombstone record with status "gone". Use this when you already have an object identifier — from search or an earlier response — and need its full record. Do not use for searching by name (use search) or for trip planning (use day_trip/plan_route).
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Object identifier, e.g. "sat:section:2fxg6" or "grinda". |
Output Schema
| Name | Required | Description |
|---|---|---|
| id | Yes | |
| url | Yes | |
| text | Yes | The full record as serialized JSON-LD. |
| title | Yes | |
| metadata | No | Extra fields such as type, category, version, license, status. |
multi_dayRead-onlyInspect
Plan a multi-day trip on the Stockholm Archipelago Trail: an overnight stay on one island, or an island hop across up to four stages, with the ferries and the walk for each day. Use this when the user wants a hike over several days, an overnight stay on an island, or to combine two or more islands. Sections take the same identifiers as fetch (sat:section:…, slug or uid), in the order they should be visited. sections and date are both OPTIONAL: omit sections and the planner picks well-served stages; omit date and it uses the next Saturday — so call this tool for ANY multi-day request ("plan a 3-day hike"), never answer from search/fetch alone. Do not use for single-day trips (use day_trip) or A→B between two islands on one day (use plan_route). ALWAYS follow this call with show_section_map for the first stage of the trip (same date) so the user sees the route on a map. IMPORTANT: every call to this tool renders a card in the conversation. Call it at most ONCE per answer, for the single option you recommend. Never use it to compare or probe alternatives. The card already shows ferry times, piers and walking times — do not restate them in your reply; add only advice, caveats and next steps.
| Name | Required | Description | Default |
|---|---|---|---|
| hub | No | Optional preferred departure hub slug from check_day_trip/day_trip responses, e.g. 'stromkajen'. Omit to let the planner pick the best. | |
| date | No | Start date, YYYYMMDD (Europe/Stockholm), e.g. 20260905. OPTIONAL — omit and the planner uses the next Saturday. | |
| lang | No | Language of the user's message: 'sv' when the user writes in Swedish, otherwise 'en'. Always pass it — labels, dates and the card are rendered in this language. | |
| nights | Yes | Number of overnight stays, 1-7, e.g. 2. | |
| sections | No | One to four section references in visiting order: satId, slug or uid — e.g. ['grinda', 'finnhamn']. |
Output Schema
| Name | Required | Description |
|---|---|---|
| hub | No | Mainland ferry hub the trip departs from. Absent for road-accessible stages (no ferry). |
| date | Yes | First day, YYYYMMDD. |
| days | No | One entry per calendar day, earliest first — including rest days (`rest: true`), so day N is the Nth day of the trip. |
| kind | Yes | |
| nights | Yes | Number of overnight stays. |
| reason | No | Only on kind "no-multi-day": why no trip could be built. |
| titles | No | Display names of the sections, same order. |
| sections | Yes | Section slugs, in the order they are visited. |
| permalink | No | Opens exactly this trip in the planner. |
| totalWalkKm | No | Total walking distance for the whole trip, km. |
| suggestedFollowUps | No | Short next steps. Offer these to the user as quick follow-up options at the end of your reply. |
pier_departuresRead-onlyInspect
List the scheduled Waxholmsbolaget ferry departures (or arrivals) at one pier or harbour of the Stockholm Archipelago Trail on a given date, within a time window: departure time, line, destination and stops on the way, arrival time at the final stop, whether advance booking is required, and which boat is the last of the day. Use this when the user asks what boats leave from or arrive at a specific pier or island ("which boats leave Grinda this afternoon?", "when is the last ferry back from Utö tonight?"). The pier can be given by name (island or pier, e.g. 'Grinda', 'Stavsnäs'), slug or id (sat:pier:…, GTFS stop id); when a name matches several piers the response lists them (kind 'ambiguous') — ask the user or pick the obvious one and call again. Renders no card. Do not use for planning a whole trip (use day_trip/plan_route) or for lodging and places (use search).
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | Latest time, HHMM or HH:MM (24 h). OPTIONAL — omit for 23:59. | |
| date | No | Date, YYYYMMDD (Europe/Stockholm), e.g. 20260905. OPTIONAL — omit for today. | |
| from | No | Earliest time, HHMM or HH:MM (24 h), e.g. '1400' for 'this afternoon'. OPTIONAL — omit for now (today) or 00:00 (other dates). | |
| lang | No | Language of the user's message: 'sv' when the user writes in Swedish, otherwise 'en'. Always pass it — labels, dates and the card are rendered in this language. | |
| pier | Yes | Pier reference: name ('Grinda', 'Södra Grinda', 'Strömkajen'), slug, sat:pier:… id or GTFS stop id. | |
| limit | No | Max rows, 1–50. OPTIONAL — default 20. | |
| direction | No | 'departures' (default) = boats leaving the pier; 'arrivals' = boats arriving at it. |
Output Schema
| Name | Required | Description |
|---|---|---|
| to | No | Window end, HH:MM |
| date | No | YYYYMMDD |
| from | No | Window start, HH:MM |
| kind | Yes | |
| pier | No | |
| total | No | Rows in the window before `limit` was applied. |
| direction | No | |
| timetable | No | kind = out-of-range: the dates the timetable covers. |
| candidates | No | kind = ambiguous: the piers that matched. |
| departures | No | Sorted by time. For arrivals the rows carry from/departure instead of to/arrival. |
| timetableValidTo | No | Last date of the loaded timetable, YYYY-MM-DD. |
| suggestedFollowUps | Yes |
place_detailsRead-onlyInspect
Get the full record for one place, stage, pier or vessel on the Stockholm Archipelago Trail by identifier: description, photo (image.contentUrl with credit/license), opening hours, website/phone, accessibility, SAT passport info and links. Use this when the user asks about a specific place ("tell me more about Arholma handel") and you have its id (sat:poi:…, sat:section:…, sat:pier:…) from a map card, search or an earlier response. Same data as fetch. Do not use for searching by name (use search) or for trip planning (use day_trip/plan_route).
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Object identifier, e.g. "sat:poi:n5d79" or "sat:section:2fxg6". | |
| lang | No | Language of the user's message: 'sv' when the user writes in Swedish, otherwise 'en'. Always pass it — labels, dates and the card are rendered in this language. |
Output Schema
| Name | Required | Description |
|---|---|---|
| id | Yes | |
| url | Yes | |
| text | Yes | The full record as serialized JSON-LD. |
| title | Yes | |
| metadata | No | Extra fields such as type, category, version, license, status. |
plan_routeRead-onlyInspect
Plan a multimodal A→B route between two trail sections (islands), or between an island and a mainland ferry hub (Strömkajen, Vaxholm, Årsta, Stavsnäs …): walk → ferry → walk, with departure/arrival times, walking distances and pier names. Use this when the user wants to travel from one island to another, out to an island from the mainland, or home from an island (or asks how to get between two places on the trail). From/to take the same identifiers as fetch (sat:section:…, slug or uid). Same section for both returns a walk-only route. Do not use for a round trip to a single island (use day_trip) or for multi-day trips (use multi_day). If the user has not named the two islands, pick two neighbouring stages with search first and then call this tool. IMPORTANT: every call to this tool renders a card in the conversation. Call it at most ONCE per answer, for the single option you recommend. Never use it to compare or probe alternatives. The card already shows ferry times, piers and walking times — do not restate them in your reply; add only advice, caveats and next steps.
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | Destination: a section reference (e.g. 'moja') or a mainland ferry hub (e.g. 'arsta'). | |
| date | No | Travel date, YYYYMMDD (Europe/Stockholm), e.g. 20260905. Defaults to today. | |
| from | Yes | Start: a section reference (satId, slug or uid, e.g. 'uto') or a mainland ferry hub (e.g. 'stromkajen', 'vaxholm', 'arsta'). | |
| lang | No | Language of the user's message: 'sv' when the user writes in Swedish, otherwise 'en'. Always pass it — labels, dates and the card are rendered in this language. | |
| time | No | Earliest departure, HHMM (24h). Defaults to 0900. |
Output Schema
| Name | Required | Description |
|---|---|---|
| to | Yes | |
| date | Yes | YYYYMMDD. |
| from | Yes | |
| time | No | Earliest departure "HHMM". |
| route | Yes | Geometry-free route result. kind "ok" carries bestAny/bestBoatOnly with walk legs (distances, pier names) and ferry legs (departure/arrival, line, booking). kind "walk-only" is a same-island walk. Other kinds describe why no route was found. |
| toTitle | No | |
| fromTitle | No | |
| permalink | No |
searchRead-onlyInspect
Search the published objects of the Stockholm Archipelago Trail: trail sections (stages), the trail itself, ferry piers, ferry vessels, reviewed public reports and points of interest (lodging, food, shops, nature). Returns matching objects with their permanent sat-identifiers. Use this when the user names or describes a place, stage, pier, vessel or POI category and you need to find its identifier before calling another tool. Do not use for general Sweden/Stockholm travel, gear or weather questions — those are outside this dataset.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Free-text search, e.g. an island name ("Grinda"), a pier, a vessel or a POI category. |
Output Schema
| Name | Required | Description |
|---|---|---|
| results | Yes | Ranked matches, best first. |
show_imagesRead-onlyInspect
Show photos of one trail section (island) of the Stockholm Archipelago Trail: the stage hero image plus photos of places (lodging, food, nature) along it, each with credit and license. Use this when the user wants to SEE what a section looks like. Takes the same identifiers as fetch (sat:section:…, slug or uid). Do not use for maps (use show_section_map).
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Section reference: satId, slug or uid, e.g. 'uto'. |
Output Schema
| Name | Required | Description |
|---|---|---|
| hero | No | |
| title | Yes | |
| photos | No | |
| section | Yes | |
| permalink | No |
show_section_mapRead-onlyInspect
Show an interactive map of one trail section (stage) of the Stockholm Archipelago Trail, with the hiking route and ferry piers. Use this when the user wants to SEE a section on a map. Takes the same identifiers as fetch (sat:section:…, slug or uid). Pass targetKm (and optionally date) to draw a shorter or longer walk instead of the full stage. Do not use for comparing several stages side by side (use search/fetch). This tool renders an interactive map card itself — NEVER build your own map, chart, image or file from geojsonUrl or the coordinates; just call the tool and let the card show. IMPORTANT: every call to this tool renders a card in the conversation. Call it at most ONCE per answer, for the single option you recommend. Never use it to compare or probe alternatives. The card already shows ferry times, piers and walking times — do not restate them in your reply; add only advice, caveats and next steps.
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | Travel date, YYYYMMDD (Europe/Stockholm), e.g. 20260905. Only used with targetKm — the walk starts at the pier that day's ferry lands at. Defaults to today. | |
| lang | No | Language of the user's message: 'sv' when the user writes in Swedish, otherwise 'en'. Always pass it — labels, dates and the card are rendered in this language. | |
| section | Yes | Section reference: satId ("sat:section:2fxg6"), slug or uid — e.g. 'uto'. | |
| towards | No | Optional named place on the island (beach, viewpoint, café) to steer the walk towards, as shown by search/fetch — e.g. 'Stora Sandvik'. | |
| targetKm | No | Desired walking distance in km, 1–60, e.g. 9. Pass when the user asks for a shorter or longer walk than the full stage (e.g. "about 9 km"). Omit for the full stage. | |
| direction | No | Optional compass direction to steer a shorter walk towards: one of N, NE, E, SE, S, SW, W, NW — e.g. 'NE' to walk towards the north-east part of the island. |
Output Schema
| Name | Required | Description |
|---|---|---|
| bbox | Yes | [west, south, east, north] |
| pois | No | Points of interest on the stage (category-coloured markers). |
| slug | Yes | |
| walk | No | Present when targetKm was passed: the actual walk that was built. |
| piers | Yes | |
| route | No | Present with targetKm: the built walk as a GeoJSON LineString ([lon, lat]). The widget draws this instead of geojsonUrl. |
| satId | Yes | |
| title | Yes | |
| permalink | Yes | |
| distanceKm | No | |
| geojsonUrl | Yes | |
| variantNote | No | Present when a requested targetKm walk could not be built: the full stage is shown instead. Tell the user this. |
| suggestedFollowUps | No | Up to three short next steps, in English (e.g. "Make the walk shorter"). Offer these to the user as quick follow-up options at the end of your reply. |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
10 tool updates
- First observed
check_day_trip - First observed
day_trip - First observed
fetch - First observed
multi_day - First observed
pier_departures - First observed
place_details - First observed
plan_route - First observed
search - First observed
show_images - First observed
show_section_map
Related MCP Connectors
Stockholm archipelago boats: realtime departures, trip planning, disruptions, island guides.
Stockholm public transport (SL): live departures, trips to addresses with exits, disruptions.
Personal sailing voyage log: trips, legs, ships, crew and GPX tracks with honest statistics.
Stockholm transit: realtime departures, trip planning, disruptions and personal commute status.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to explore Swiss hiking routes with real-time closures, weather, public transport, and POIs, including GPX generation.1MIT

onvaou-itineraires-mcpofficial
AlicenseAqualityCmaintenanceBike, e-bike, kick scooter, motorcycle, wheelchair and walking routes across Europe, with up to three variants (safe, balanced, fast) and safety indicators such as cycle lane, main road and unpaved shares.176 npmMIT- AlicenseBqualityBmaintenanceEnables Claude to design reliable hiking routes on real trails, computing accurate distance and elevation gain, locating notable points, technical passages, regulated areas, bivouac and stage options, and weather, with automatic validation across roughly 35 rules. Routes can be exported as GPX (including one file per day), Obsidian notes, HTML maps, and printable roadbooks.231MIT

Departi MCP Serverofficial
AlicenseAqualityCmaintenanceTravel compliance and trip planning for digital nomads — visa requirements, tax residency analysis, Schengen 90/180-day tracking, and curated accommodation, transport, and experience search across 189 European destinations.7MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.