playbooks

home / mcp / polarsteps mcp server

Polarsteps MCP Server

An unofficial Polarsteps MCP Server enabling models to interact with the Polarsteps API

Installation
Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "remuzel-polarsteps-mcp": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/remuzel/polarsteps-mcp",
        "polarsteps-mcp"
      ],
      "env": {
        "POLARSTEPS_REMEMBER_TOKEN": "your_remember_token_here"
      }
    }
  }
}

This MCP server lets Claude and other AI assistants access Polarsteps travel data by querying user profiles, trips, and travel statistics. It enables natural language questions about travel history, destinations, and achievements, helping you build smarter AI interactions around Polarsteps data.

How to use

You use this MCP server by running it alongside an MCP client (such as Claude Desktop) and configuring the client to connect to the Polarsteps MCP server. The server exposes travel data through user-friendly queries like profile info, trip details, and travel statistics. Use natural language prompts to ask about a user’s trips, destinations, and travel milestones.

To connect your MCP client, configure the MCP server with the provided settings and supply your Polarsteps remember_token for authentication. This token is read from your Polarsteps account and securely passed to the MCP runtime when you start the server.

Common usage patterns include asking for travel statistics for a specific username, requesting details about a particular trip, or querying recommended destinations based on a user’s travel history. The server supports fuzzy matching for destination names and trip themes.

When you are ready, you can run the MCP command from your client to connect to the Polarsteps MCP server, then begin asking questions about profiles, trips, and travel analytics.

How to install

Prerequisites you need before installation: Node.js runtime and a compatible MCP client that supports stdio-based servers. You will also need a Polarsteps remember_token for authentication.

# Quick start using the MCP client tool
npx -y @smithery/cli install @remuzel/polarsteps-mcp --client claude

Next, set your Polarsteps token in your environment so the MCP server can authenticate to Polarsteps APIs.

export POLARSTEPS_REMEMBER_TOKEN="your_remember_token_here"

Configure the client in your MCP setup to point to the Polarsteps MCP server. The recommended stdio configuration uses the uvx runtime and runs the polarsteps-mcp package directly.

{
  "mcpServers": {
    "polarsteps": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/remuzel/polarsteps-mcp", "polarsteps-mcp"],
      "env": {
        "POLARSTEPS_REMEMBER_TOKEN": "your_remember_token_here"
      }
    }
  }
}

Additional content

Configuration notes: your Polarsteps remember_token is required to authenticate requests. The token is retrieved from the Polarsteps web interface via browser developer tools and cookies. You should store the token securely and reference it from the MCP runtime environment.

Security considerations: treat the remember_token as sensitive credentials. Do not share tokens or commit them to version control. Use environment variables to protect tokens in your deployment.

Available tools

getUserProfile

Fetches user profile information, social stats, and travel metrics for a Polarsteps user.

getTripData

Retrieves detailed trip information, timelines, and locations for a specified user.

smartSearch

Searches trips by destination, theme, or keywords with fuzzy matching.

travelAnalytics

Returns comprehensive travel statistics and achievements for a user.