Polarsteps MCP Server

Export and import trips and steps.

Hosted MCP Server

npx add-mcp 'https://cotlet.dev/mcp/v1/polarsteps'

Installs into Claude Code, Codex, Cursor and more

Documentation

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

Polarsteps API and MCP server: Let your AI agent keep your Polarsteps trips.

Polarsteps has no public API, no MCP server and no developer program (checked 24 Oct 2026). Cotlet runs 14 Polarsteps tools hosted, over MCP for agents and REST for scripts.

Read your Polarsteps trips and stories with an agent or a script. Use MCP or REST to prepare travel drafts, comment digests and trip backups.

MCP setup REST API guide

Free 7-day trial, no card
Unofficial, not affiliated with Polarsteps
Page: https://cotlet.dev/integrations/polarsteps-api-mcp-server

What can you automate in Polarsteps?

Add the day's step with photos
Answer follower comments
Export one trip as GPX
Rebuild a past trip from a CSV
Proofread before a Travel Book
Draft a blog post from a trip

Does Polarsteps have an MCP server or an API?

"Download my data" is the one official way out: an archive of every trip on the account, sent as an email link. It cannot pick one trip and it writes nothing back.
No Zapier app and no n8n node for Polarsteps. Its AI Trip Planner lives inside the app and does not connect to your agent.
The one community MCP server on GitHub reads trips and stats from your computer, on a cookie you copy. It has no write tools.

What you need	Download my data	GitHub MCP server	Cotlet
Read trips and step stories	Whole account, by email	Read only	Yes, one trip or all
Export one trip as GPX or Markdown	No	No	Yes
Add or import steps, fix their text	No	No	Yes, after your OK
Reply to comments, set trip privacy	No	No	Yes, after your OK
Runs with your computer off	Yes	No	Yes, hosted
Fixed for you when Polarsteps changes	Yes	Fix open since Jul 2026	Yes, tested every 12 h

Checked 24 Oct 2026. Sources: Polarsteps Help: How can I export a copy of my data?, Polarsteps Help: What are steps and how do I add or edit them?, Polarsteps Terms of Use, remuzel/polarsteps-mcp

How does Cotlet connect to Polarsteps?

Sign in to Polarsteps. Use your own account in its Cotlet Cloud Browser.
Choose MCP or REST. Connect your agent or create a Cotlet API key.
Run your workflow. Ask your agent or send an HTTP request.

We never save your Polarsteps password, and no step, reply or privacy change goes out without your OK.

Connect Polarsteps to your agent or workflow

Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.

Enable Polarsteps for agents. Create a Cotlet account, log in to Polarsteps in its Cloud Browser, then press Enable for agents.
Add the Cotlet address. Put https://cotlet.dev/mcp/v1 in the MCP or connector settings of your agent.
Sign in or paste a key. Chat apps sign you in to Cotlet; editors and scripts take an API key from the console.

One address for all your apps, https://cotlet.dev/mcp/v1, carries the Polarsteps tools as well. If you enable Polarsteps after you connect, refresh the connector so the agent sees them.

Claude:

Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet-polarsteps \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"

ChatGPT:

Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth

Cursor:

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet-polarsteps": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet-polarsteps]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

n8n:

MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: polarsteps_read

Make, Zapier:

Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: polarsteps_write

How to use the Polarsteps REST API

Create your Cotlet API key

Sign in to your Polarsteps account in its Cotlet Cloud Browser and enable the app for agents. These workflows read your own trips, not followed accounts.

Create a Cotlet API key with access to Polarsteps and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Make your first Polarsteps API request

cURL: list_trips:

curl "https://cotlet.dev/api/v1/polarsteps/trips?status=all&limit=10" \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read trip IDs and request their stories

A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.

Illustrative response excerpt:

{
  "status": "success",
  "app": "polarsteps",
  "tool": "list_trips",
  "result": {
    "trips": [
      {
        "trip_id": "18452237",
        "name": "Portugal by train",
        "steps": 9,
        "privacy": "followers"
      }
    ]
  }
}

Read result.trips. This operation has a limit of 50 by default and 100 at most, with no cursor or offset input.

Do not treat a limited trip list as an exhaustive export when your account exceeds that limit. Use the returned trip_id for step reads and trip exports.

list_steps supports since without cursor pagination. get_step returns the full story and media links; export_trip download links expire after one hour.

Polarsteps workflows for agents and automations

Tool	Connect through	Example workflow
Python or Node.js	REST API	Read trip IDs and export selected trips as GPX files to your storage before their download links expire.
n8n	HTTP Request	Combine `list_steps` and `get_step` into a trip-blog draft with the story and selected media links.
Make	HTTP > Make a request	Read step comments into a follower-comment digest, remembering comment IDs and comparing updates without replying.

Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads Polarsteps; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.

Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.

The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.

Polarsteps API endpoints and MCP tools

Trips, privacy and exports

Only trips on your own account, not ones you follow. A new trip starts as Only me unless you pick a level. Export links last 1 hour, photos only when you ask.

List trips (list_trips, read): Your trips, newest first, with dates, privacy level, distance and step count.
Get trip (get_trip, read): One trip: name, summary, dates, privacy, Travel Buddies, distance and countries.
Get travel stats (get_travel_stats, read): Countries visited, total kilometers, number of trips and steps on your profile.
Export trip (export_trip, read): One trip as a download link, valid for 1 hour: route, steps and photo links.
Create trip (create_trip, write, asks first): New trip, past or upcoming, with the privacy level you pick.
Set trip privacy (set_trip_privacy, write, asks first): Choose who can see a trip: only you, your followers or everyone.

Steps, stories and photos

A new date or place moves the step on the route line. import_steps takes up to 50 steps a call. No tool deletes a step.

List steps (list_steps, read): Steps of a trip in order, with place, country, date, title and photo count.
Get step (get_step, read): Full step: story text, place and coordinates, date, photo and video links.
Add step (add_step, write, asks first): Add a step to a trip with a story and photos. People who can see the trip see it.
Import steps (import_steps, write, asks first): Add many steps at once, e.g. a past trip from a CSV, sorted by date.
Update step (update_step, write, asks first): Change the title, story, place or date of a step.
Add step photos (add_step_photos, write, asks first): Add photos or videos to an existing step.

Comments

Comments on your own steps. A reply shows under your name to everyone who can see the trip.

List step comments (list_step_comments, read): Comments your followers left on a step, with author and date.
Reply to step comment (reply_to_step_comment, write, asks first): Reply to a follower comment on one of your steps, as you.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/polarsteps-api-mcp-server#tools

Who can see my Polarsteps session, and how do I revoke it?

What we store. Your logged-in Polarsteps profile, AES-256-GCM, in Finland. Not your password.
What your agent gets. Polarsteps tools only. No cookie, no remember token.
What the session sees. What you see: your trips, Only me ones too, steps, photos, comments.
What no tool touches. Followers, follow requests, secret links, live location, Travel Book orders, Plus.
If Polarsteps logs you out. You get an email with a sign-in link. We never log in for you.
How to cut access. Disable for agents, reset the browser or delete the key. The next call stops.

A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). No SOC 2 report or third-party pentest yet.

Is it against Polarsteps' terms? Account safety

use manual or automated software, devices, or other processes to "crawl" or "spider" any page of the Platform; harvest, scrape, copy or mirror any Content from the Service

Polarsteps Terms of Use, Rules and Conduct

Every Polarsteps tool without an API runs into this clause, the GitHub server included. After Follow the Money pulled public data on about 23 million users in September 2026, Polarsteps added "even stricter API controls to prevent large-scale access to our public user data" (statement). Those controls aim at other people's trips; our tools open only your own. We found no public case of a Polarsteps account closed for automation (checked 24 Oct 2026).

How we keep your account looking like you:

Your own account, logged in by you
Your trips only, never other travellers' profiles
One Cloud Browser with its own IP and cookies
Steps, replies and privacy changes wait for your OK
You finish sign-in and 2FA yourself
If Polarsteps objects, we pause Polarsteps for everyone within 24 h

The terms also ban "any form of auto-responder". Read each comment reply before you approve it, and keep a backfill of an old trip to a few imports, not hundreds of single steps.

What happens when Polarsteps changes?

12 h between tests of trips, steps, exports and stats
24 h between tests of steps, photos and replies others see
$0 for calls to a tool paused for a fix

Polarsteps does change under you. Since July 2026 the app's backend answers 404 to requests without a version header, and the GitHub wrapper behind the community MCP server still waits for that fix (pull request). On Cotlet a fix like that is ours to make, not yours.

Approvals, undo and mistakes

Checks the rows. Every place in your CSV needs a date.
Creates it private. The past trip starts as Only me.
Waits for your OK. One approval in your Cotlet console covers each batch of 50.
Reports back. Steps added, photos attached, rows it asked about.

Action	Undo
Add or import steps	No delete tool, remove them in Polarsteps
Create a trip	No delete tool, delete it in Polarsteps
Edit a step	Yes, the agent reads the old text first
Change trip privacy	Yes, same tool, but followers may have seen it
Reply to a comment	No tool takes it back

7 of 14 tools ask first: every write. The 7 reads never do, exports included. Turn the wait off per tool once you trust a scheduled job, or enable Polarsteps read only.

MCP call:

{
  "name": "add_step",
  "arguments": {
    "trip_id": "18452237",
    "place": "Alfama, Lisbon, Portugal",
    "date": "2026-10-09T19:30:00+01:00",
    "title": "Fado night in Alfama",
    "story": "Got lost in the old town, then found a tiny fado bar with six tables.",
    "photo_urls": [
      "https://example.com/photos/alfama-1.jpg",
      "https://example.com/photos/alfama-2.jpg"
    ]
  }
}

REST:

curl -X POST https://cotlet.dev/api/v1/polarsteps/trips/18452237/steps \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"place":"Alfama, Lisbon, Portugal","date":"2026-10-09T19:30:00+01:00","title":"Fado night in Alfama","story":"Got lost in the old town, then found a tiny fado bar with six tables.","photo_urls":["https://example.com/photos/alfama-1.jpg","https://example.com/photos/alfama-2.jpg"]}'

Tool output:

{
  "step_id": "231908554",
  "trip_id": "18452237",
  "title": "Fado night in Alfama",
  "place": "Lisbon, Portugal",
  "date": "2026-10-09T19:30:00+01:00",
  "photos": 2
}

Scripts and cron jobs reach the same tools over REST under /api/v1/polarsteps, with the same key and price. A call Polarsteps refuses, such as a step on a trip that is not yours, fails and costs no credits. The tools table lists the REST path of each tool.

How much does the Polarsteps MCP server cost?

About $20 a month for a month with one 17-day trip, 3,380 credits. Polarsteps itself stays free.

Job	Calls	Credits
Add the day's step with photos	2 × 17	340
Reply to new comments, each trip day	5 × 17	850
Proofread 25 steps for the Travel Book	39 × 1	390
Draft a blog post from the trip	27 × 1	270
Export the trip as GPX and Markdown	3 × 1	30
Cloud Browser, 30 days		1,500
Total		3,380

Free 7-day trial, no card
10 credits per successful call, MCP or REST
50 credits a day for the Cloud Browser
No Polarsteps Plus needed for any tool

17 days is the average trip of German Polarsteps travellers in 2025, from Polarsteps' Year in Travel report. Polarsteps publishes no steps per trip, so the 25 steps are our guess. Dollars at the $29 pack rate.

Polarsteps MCP server on GitHub, export tools or hosted: which to use

Option	What it does	Where it stops
remuzel/polarsteps-mcp	The only Polarsteps MCP server: 7 read tools for profiles, trips, stats and trip search, MIT, 2 stars.	No writes, runs on your computer with your `remember_token` cookie. Last commit 11 Jul 2025; the fix for the backend's 404s waits in an open pull request since 30 Jul 2026.
etigui/polarsteps-trip-backup	Python backup of trips, steps and media through the app's backend.	Backup only; it already had to follow a renamed field.
Export converters	polarsteps-travel-book-creator (PDF, 13 stars), wanderbound (photo album) and several GPX scripts.	Work on the "Download my data" archive, so each run waits for the email of the whole account.
WordPress plugins	integrate-polarsteps and polarsteps-wordpress-import pull steps into a blog.	One way, into WordPress. The first has had no push since 2019.

We found no paid or hosted tool that works inside a Polarsteps account. Use a converter if a PDF or a GPX from an old archive is all you need. Use the GitHub server if read-only access on your own machine is enough and you can patch it. Use Cotlet when your agent should also write steps, answer comments and export single trips.

Also listed on: Odel, mcpbeat

Who runs Cotlet

Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), working since 2019, founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev about the Polarsteps tools.

Polarsteps API and MCP: questions

Can I use the Polarsteps API without an AI agent?

Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.

How do I get access?

Sign up free at https://cotlet.dev, open Polarsteps under Integrations in the console and log in to Polarsteps in its Cloud Browser. Your free trial starts when you sign up, no card needed.

How do I connect Polarsteps to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Polarsteps once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Polarsteps account through Cotlet, in their phone apps too.

What can ChatGPT do in Polarsteps?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Polarsteps: export a single trip as GPX; turn a trip into a blog post; import a past trip from a spreadsheet. You ask in plain words, and anything that reaches other people waits for your OK first.

Can my agent export trips I follow?

No. Cotlet works in your own Polarsteps account and lists the trips on it. Trips you only follow are not part of list_trips.

Who sees a step my agent adds?

Everyone who can see that trip. Polarsteps trips have three privacy levels, Only me, Followers and Everyone, and a new trip is set to Followers in the app. add_step asks for your OK by default.

Does Polarsteps have webhooks?

No. Polarsteps sends no events out. To catch new comments, run your agent on a schedule with list_steps and its since date, then list_step_comments on the steps that have new ones.

Do I need Polarsteps Plus?

No. Every tool works on the free plan. Plus (€8.99 a month or €29.99 a year on 24 Oct 2026) adds 3D maps, map styles, step stats and up to 10 Travel Buddies instead of 5.

Can my agent delete a trip or a step?

No. None of the tools deletes anything. Remove a step or a trip yourself in the Polarsteps app or on polarsteps.com.

Is the MCP server different from the REST API?

Only the way in. Both have the same 14 tools, inputs and answers, one API key and one price. Agents use MCP; scripts, cron jobs and HTTP steps use REST.

Is Cotlet affiliated with Polarsteps?

No. Cotlet is independent and not affiliated with Polarsteps.

Give your AI agents your signed-in browser.

Product: Integrations · How it works · Pricing · Security

Resources: Blog · API docs · Help center · Changelog · GitHub

Solutions: For developers · For automation agencies

Company: About · AI info: company facts · Contact

Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors

Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.