Connectors / Hobbies, outdoors & playing sport

Stockholm Archipelago Trail

Plan hikes & ferry routes

The Stockholm Archipelago Trail app brings Sweden's 270 km island hiking trail into your AI. Ask about any of the trail's ~20 island stages — from Arholma in the north to Landsort in the south — and get structured, up-to-date details: distance, difficulty, harbours and piers, and points of interest such as cafés, viewpoints, swimming spots, and shelters.

What you can ask

Plan a 3-day hike on the Stockholm Archipelago Trail.
Example path

MCP connector

Server URL: https://map.stockholmarchipelagotrail.com/mcp
Login: None
Protocol: MCP 2025-06-18
Instructions: Read-only access to Stockholm Archipelago Trail objects (CC BY 4.0). Use search to find objects, fetch to get a full record by id. Ids are permanent (sat:<type>:<uid>). Card rule: , , and each render a card in the conversation on EVERY call — call each of them at most once per answer, only for the option you recommend. To compare dates, hubs or stages, use (same data as , renders no card), search and fetch. Multi-day, overnight or island-hopping requests: if the user has not named stages, pick one or two with search, then ALWAYS call with those sections — never answer such requests from search/fetch alone. Same for walk-ferry-walk between islands: pick the stages, then call . The cards already show ferry departure/arrival times, piers, line numbers and walking times. Never restate those in your text: add only advice, caveats, booking notes and next steps. When you mention a place (café, beach, viewpoint …) that appears in a map result, link its name to the url given for it.

Tools

Reads data10

Skills

None in the store listings or on the server

MCP connector

Server URL

https://map.stockholmarchipelagotrail.com/mcp

None

Protocol

MCP 2025-06-18

Instructions

Read-only access to Stockholm Archipelago Trail objects (CC BY 4.0). Use search to find objects, fetch to get a full record by id. Ids are permanent (sat:<type>:<uid>). Card rule: , , and each render a card in the conversation on EVERY call — call each of them at most once per answer, only for the option you recommend. To compare dates, hubs or stages, use (same data as , renders no card), search and fetch. Multi-day, overnight or island-hopping requests: if the user has not named stages, pick one or two with search, then ALWAYS call with those sections — never answer such requests from search/fetch alone. Same for walk-ferry-walk between islands: pick the stages, then call . The cards already show ferry departure/arrival times, piers, line numbers and walking times. Never restate those in your text: add only advice, caveats, booking notes and next steps. When you mention a place (café, beach, viewpoint …) that appears in a map result, link its name to the url given for it.