Alltrails MCP

Name: Alltrails MCP
Author: chrischall

by chrischallversion 3.2.1i★ –iRuns on your computer

Registry nameio.github.chrischall/alltrails-mcp

Install

Overview

Description from the maker (original English)

Unofficial AllTrails MCP for Claude — search trails, get details, reviews, photos, saved lists

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiEarly↓ 694/wk · ★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Design, images & audio

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: ALLTRAILS_USER_ID, ALLTRAILS_REQUEST_TIMEOUT_MS, ALLTRAILS_DEBUG_LOG, ALLTRAILS_WS_PORT, ALLTRAILS_LOCALE, ALLTRAILS_CALLER

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "alltrails": {
      "command": "npx",
      "args": [
        "-y",
        "alltrails-mcp"
      ],
      "env": {
        "ALLTRAILS_USER_ID": "your-value",
        "ALLTRAILS_REQUEST_TIMEOUT_MS": "your-value",
        "ALLTRAILS_DEBUG_LOG": "your-value",
        "ALLTRAILS_WS_PORT": "your-value",
        "ALLTRAILS_LOCALE": "your-value",
        "ALLTRAILS_CALLER": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add alltrails --env ALLTRAILS_USER_ID=your-value --env ALLTRAILS_REQUEST_TIMEOUT_MS=your-value --env ALLTRAILS_DEBUG_LOG=your-value --env ALLTRAILS_WS_PORT=your-value --env ALLTRAILS_LOCALE=your-value --env ALLTRAILS_CALLER=your-value -- npx -y alltrails-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "alltrails": {
      "command": "npx",
      "args": [
        "-y",
        "alltrails-mcp"
      ],
      "env": {
        "ALLTRAILS_USER_ID": "your-value",
        "ALLTRAILS_REQUEST_TIMEOUT_MS": "your-value",
        "ALLTRAILS_DEBUG_LOG": "your-value",
        "ALLTRAILS_WS_PORT": "your-value",
        "ALLTRAILS_LOCALE": "your-value",
        "ALLTRAILS_CALLER": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "alltrails": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "alltrails-mcp"
      ],
      "env": {
        "ALLTRAILS_USER_ID": "your-value",
        "ALLTRAILS_REQUEST_TIMEOUT_MS": "your-value",
        "ALLTRAILS_DEBUG_LOG": "your-value",
        "ALLTRAILS_WS_PORT": "your-value",
        "ALLTRAILS_LOCALE": "your-value",
        "ALLTRAILS_CALLER": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

ALLTRAILS_USER_ID env
Optional numeric AllTrails user id for the per-user tools (saved lists, completed trails, feed). If omitted, those tools resolve the signed-in user via /api/alltrails/me.
ALLTRAILS_REQUEST_TIMEOUT_MS env
Per-request timeout in ms (default 30000).
ALLTRAILS_DEBUG_LOG env
1/true/yes/on logs each request/response to stderr — method, path, status, response size, and a redacted 200-char request-body prefix (response bodies are never logged).
ALLTRAILS_WS_PORT env
fetchproxy concentrator port (default 37149, shared by the whole fetchproxy fleet — override only for local dev/tests).
ALLTRAILS_LOCALE env
Overrides the x-language-locale request header (default "en-US").
ALLTRAILS_CALLER env
Overrides the x-at-caller request header (default "Mugen").

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account chrischall, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Design, images & audioi

More stars than 0% of the other 2787 servers in this category
Published to the registry more recently than 90% of the other 2787 servers in this category
Basic checks equal to or better than 100% of the other 2787 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Alltrails MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (3.2.1) reached the registry 4 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Figma Context MCP, Claude Real Video, Figma MCP Server

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Figma Context MCP

Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.

by GLipsWidely used↓ 161.2K/wk★ 16.2KUpdated 5 months ago

Runs on your computer

Install

Claude Real Video

Let any LLM watch a video locally — and search everything it has ever watched.

by HUANGCHIHHUNGLeoWidely used↓ 1.1K/wk★ 2.3KUpdated 2 months ago

Runs on your computer

Install

Figma MCP Server

Figma’s official server gives AI your design data so it can turn designs into code or describe them accurately. Connects to Figma’s cloud.

by figmaGrowing★ 2.2KUpdated 13 months ago

Runs in the cloud✓ mcp.figma.com

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

AllTrails MCP

A Model Context Protocol server that connects Claude to AllTrails, giving you natural-language access to trail search, trail details, reviews, photos, weather, and your own saved lists and hiking history.

[!WARNING]

AI-developed project. This codebase was entirely built and is actively maintained by Claude. No human has audited the implementation. Review all code and tool permissions before use.

[!CAUTION]

Unofficial and unsupported. AllTrails has no public API. This server reverse-engineers the internal API used by alltrails.com. That API is fronted by DataDome bot protection and governed by AllTrails' Terms of Service. It may break without notice, and automated access may violate their ToS — a prior third-party AllTrails project was disabled at AllTrails' request. Use this only for your own account, at your own discretion.

What you can do

Ask Claude things like:

*"Find waterfall trails near Portland, Oregon"*
*"What's the AllTrails rating and length of trail 10236086?"*
*"Summarize the recent reviews for this trail"*
*"What trails have I marked completed?"*
*"Show me the trails on my saved 'weekend hikes' list"*

Requirements

Claude Desktop (or any MCP host)
Node.js 22.5 or later
The ContextMint Bridge browser extension and a signed-in alltrails.com tab (see Authentication)

Acknowledgement of Terms

By using this MCP server, you acknowledge and agree to the following:

1. This server accesses AllTrails using your own signed-in session. It reuses the cookies from your own browser session; it cannot access anyone else's account or private data.

2. [AllTrails' Terms of Service](https://www.alltrails.com/terms) govern your use of this server, just as they govern your direct use of AllTrails. AllTrails restricts automated access and scraping, and fronts its API with bot protection. Automated use through this server may breach those terms. You are agreeing to AllTrails' terms every time you invoke a tool.

3. Personal use only. This project is not affiliated with, endorsed by, or sponsored by AllTrails, LLC. It is a personal automation tool. Do not use it to bulk-extract AllTrails' data, to build a competing product, or in any way that burdens their service.

4. You accept full responsibility for any consequences — technical (rate-limiting, CAPTCHA challenges, account action) or otherwise. The maintainer provides no warranty and no support.

This section is the maintainer's good-faith summary — it is not legal advice and does not modify or supersede AllTrails' actual ToS.

Installation

1. Clone and build

git clone https://github.com/chrischall/alltrails-mcp.git

cd alltrails-mcp npm install npm run build

2. Add to Claude Desktop

Edit your Claude Desktop config file:

Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the alltrails entry inside "mcpServers" (create the key if it doesn't exist):

"mcpServers": { "alltrails": { "command": "node", "args": ["/absolute/path/to/alltrails-mcp/dist/index.js"] } } }

Replace /absolute/path/to/alltrails-mcp with the path where you cloned the repo.

3. Restart Claude Desktop

Quit completely (Cmd+Q on Mac, not just close the window) and relaunch.

4. Verify

Ask Claude: *"Search AllTrails for trails near me."*

Authentication

AllTrails fronts its internal API with DataDome bot protection, and DataDome fingerprints the HTTP client itself — a cookie copied out of the browser and replayed from Node gets rejected even while the browser sails through. So the fetchproxy bridge is required: every API request runs as a same-origin fetch inside your own signed-in alltrails.com tab, reusing your authenticated session. There is no stored-cookie mode.

Requirements: the ContextMint Bridge browser extension installed (Chrome: download the chrome zip from the releases page and load it unpacked — use Chrome for now; Safari support will ship inside the ContextMint app, which has no public download yet), a signed-in alltrails.com tab open, and a one-time pair-code approval on first use (the trust persists).

ContextMint Bridge is the fetchproxy browser extension under its new name, from the same maintainer — fetchproxy's own README (https://github.com/chrischall/fetchproxy#extension) points to it. Its source is public at https://github.com/nullnet-app/contextmint-bridge: build it yourself, or check a release zip against the .sha256 file published beside it (shasum -a 256 -c contextmint-bridge-chrome- .zip.sha256).

The x-at-key app key AllTrails' own client sends is never stored in this repo or your config — the server captures the live value from your tab's own API traffic on first need, keeps it in memory only, and re-captures automatically if AllTrails rotates it. The alltrails_healthcheck tool round-trips a probe through the bridge and tells you which hop broke.

Configuration

Env var	Required	Purpose
`ALLTRAILS_USER_ID`	No	Numeric user id for the per-user tools; defaults to the signed-in user via `/api/alltrails/me`.
`ALLTRAILS_WS_PORT`	No	fetchproxy concentrator port (default `37149`, shared by the whole fetchproxy fleet — override only for local dev/tests).
`ALLTRAILS_LOCALE` / `ALLTRAILS_CALLER`	No	Override the corresponding request headers.
`ALLTRAILS_REQUEST_TIMEOUT_MS`	No	Per-request timeout in ms (default `30000`), applied on both paths.
`ALLTRAILS_DEBUG_LOG`	No	`1`/`true`/`yes`/`on` logs each request/response to stderr — method, path, status, response size, and a redacted 200-char request-body prefix (response bodies are never logged).

Available tools

All tools are read-only — this server never writes to AllTrails.

Tool	What it does
`alltrails_search`	Search AllTrails by trail or place name — free-text queries use the same suggestions endpoint as the alltrails.com search box (`types: ["trail"]` narrows to trails only)
`alltrails_resolve_location`	Resolve a place name to AllTrails location records (country/state/city/area/POI) with each one's kind, coordinates, slug, and disambiguation label
`alltrails_get_trail`	Trail details — name, overview, length, elevation gain, difficulty, rating, route type, location (`detail`: `basic`/`medium`/`offline` picks what AllTrails sends us)
`alltrails_get_trail_reviews`	User reviews for a trail — `{user, rating, comment}` each
`alltrails_get_trail_photos`	Photos for a trail — slim records with a fetchable image `url`
`alltrails_get_trail_gpx`	Export a trail's route as GPX 1.1 (track points + elevation)
`alltrails_get_trail_weather`	Weather overview for a trail
`alltrails_get_profile`	The signed-in user's profile
`alltrails_list_user_lists`	A user's saved lists / favorites
`alltrails_get_list_items`	The trails saved in a list, by list id — ordered `{trailId, type, order, notes, addedAt}`, hydrate each via `get_trail`
`alltrails_list_completed_trails`	A user's completed trails
`alltrails_get_activity_feed`	A user's activity feed (`feed`: `local`/`timeline`/`personal` for the items, omit for the directory; `cursor` paginates)
`alltrails_healthcheck`	Round-trips a probe through the fetchproxy bridge and reports role/port/timing plus a plain-English hint about which hop broke

The per-user tools default to the signed-in user (resolved via /api/alltrails/me or ALLTRAILS_USER_ID); pass userId to target a public profile.

Response shape: `view`

alltrails_search, alltrails_get_trail, alltrails_get_trail_reviews, alltrails_get_trail_photos, alltrails_get_list_items and alltrails_get_activity_feed take a view parameter with two rungs (the feed has a third, brief):

`view`	What you get
`compact`	The default. The slim projection described in the table above — the fields a caller acts on. Nothing to pass.
`full`	AllTrails' whole untouched record.
`brief`	`alltrails_get_activity_feed` only: one line per item, `who: what — —` , reading the `timeline` feed when none is named. The context-groups (mcp-host) canonical what's new read.

Compact is the default deliberately. These projections existed before, behind compact: false and a tool description asking the caller to please opt in — and an efficiency that has to be requested is one that usually is not. Ask for view: "full" when you need a field the projection drops; the commonest is route geometry from alltrails_get_trail.

`view` is not `detail`. alltrails_get_trail also takes detail

(basic/medium/offline), and that one is a passthrough to AllTrails —

it decides what the API sends *us*. view decides what this server hands

*you*. Route geometry needs both: detail: "offline" to fetch it and

view: "full" to keep it. The collision is exactly why the fleet parameter is

named view.

One projection is not a subset: alltrails_get_trail_photos' url is

derived by the compact rung (AllTrails' record carries no image URL), so

view: "full" does not contain it.

Troubleshooting

403 Forbidden — AllTrails' DataDome protection rejected the request. This usually means the tab isn't signed in (or DataDome is challenging it) — sign into alltrails.com in an open tab and retry.

"AllTrails bridge: …" — the bridge itself failed before reaching AllTrails (extension not running, pairing not approved, no tab). Run alltrails_healthcheck for a diagnosis, and check the ContextMint Bridge extension popup.

"AllTrails: capturing the x-at-key app key failed…" — the key is read off a request your tab makes while the call is waiting, and an idle tab makes none. Refreshing first does not help: the extension only listens for the duration of the call, so a reload that finished before it started happened while nothing was listening. Run the tool again and reload a signed-in www.alltrails.com tab while it is running.

Empty / unexpected results — the internal AllTrails endpoints are undocumented and change over time; responses may shift. Enable ALLTRAILS_DEBUG_LOG=1 to trace each request's method, path, status and response size on stderr.

Development

npm test         # run the vitest suite

npm run build # tsc → dist/, then esbuild bundle → dist/bundle.js npm run dev # node --env-file=.env dist/index.js (requires built dist)

vitest.config.ts enforces 100% coverage on src/** (except the stdio entry point). Main is protected — all changes land via PR. See CLAUDE.md for the full PR + release flow.

Project structure

src/

index.ts MCP server entry (runMcp + StdioServerTransport) protocol.ts Wire-level constants (BASE_URL, app key, headers) transport.ts createAllTrailsTransport(): the fetchproxy bridge transport client.ts AllTrailsClient — bridge requests, live x-at-key capture, 429 retry config.ts Env parsing (api key, headers, timeout, port, user id, debug) valida

Only the beginning is shown; read the rest in the repo

Alltrails MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Design, images & audioi

Common questions

Alternatives

Figma Context MCP

Claude Real Video

Figma MCP Server

README from the maker

AllTrails MCP

What you can do

Requirements

Acknowledgement of Terms

Installation

1. Clone and build

2. Add to Claude Desktop

3. Restart Claude Desktop

4. Verify

Authentication

Configuration

Available tools

Response shape: view

Troubleshooting

Development

Project structure

Response shape: `view`