Polarsteps MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POLARSTEPS_REMEMBER_TOKEN | Yes | Your Polarsteps remember_token cookie value for authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_user_profileC | Get a users' profile overview including their living location and their number of countries visited & trips. |
| get_user_socialC | Get a users' social information including: followers, followees, their count and if they're considered popular. |
| get_user_statsB | Get available travel statistics and metrics for a Polarsteps user, including countries visited, total distance traveled, trip counts, and detailed travel analytics. Perfect for getting a complete picture of someone's travel history and achievements. |
| get_tripA | Get comprehensive details about a specific trip including summary, timeline, route information, individual steps/locations, weather data, and engagement metrics. Use after get_trip_log when you need detailed information about specific locations or comprehensive trip data. |
| get_trip_logB | Get an overview of the specific trip; this includes just a list of summarized steps, each including timestamp/title/description/location. Use this first for trip overviews before diving into detailed information. |
| get_tripsA | Fetch a list of a user's recent trips with summary information including trip names, dates, duration, and basic stats. Ideal for browsing someone's travel history or finding trip IDs for detailed exploration. Use n_trips parameter to control how many recent trips to retrieve (default: 5). |
| search_tripsA | Search through a user's trips by name/title using fuzzy matching to find specific trips. Ideal for finding trips by destination (e.g., 'japan', 'italy'), themes (e.g., 'honeymoon', 'business'), or partial name matches. Supports flexible search terms that don't need to match exactly - the fuzzy matching will find relevant trips even with approximate spelling or partial keywords. Use this as the first step when looking for specific trips by destination, theme, or name. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
The tools are mostly distinct with clear purposes, but there is some overlap between get_trip and get_trip_log that could cause confusion. get_trip_log is described as an 'overview' with summarized steps, while get_trip provides 'comprehensive details', but the descriptions suggest using get_trip_log first before get_trip, which might lead to misselection if an agent needs just basic info versus full details. Other tools like get_user_profile, get_user_social, and get_user_stats are well-differentiated.
All tool names follow a consistent verb_noun pattern with underscores, such as get_trip, get_trips, get_user_profile, and search_trips. There are no deviations in naming conventions, making the set predictable and easy to understand for an agent.
With 7 tools, the server is well-scoped for a Polarsteps travel data domain. Each tool serves a specific purpose, from fetching user profiles and social info to retrieving trip details and searching, without feeling too sparse or overloaded. The count aligns well with the apparent scope of accessing travel history and user data.
The tool set covers key aspects of the Polarsteps domain, including user profiles, social information, statistics, and trip retrieval with search capabilities. However, there are minor gaps, such as no tools for updating or creating trips (e.g., create_trip or update_trip), which might limit full CRUD operations, but the existing tools support comprehensive read and search workflows effectively.