alltrails

alltrails-mcp

Unofficial MCP server for AllTrails — read-only access to trail search, details, reviews, photos, weather, and a signed-in user's saved lists / completed trails / activity feed.

⚠️ AllTrails has no public API. This server reverse-engineers the internal one used by alltrails.com, which is fronted by DataDome bot protection and governed by AllTrails' Terms of Service. It may break at any time, and automated use may violate their ToS. Use at your own discretion for your own account.

• npm: npmjs.com/package/alltrails-mcp
• Source: github.com/chrischall/alltrails-mcp

Setup

Add to .mcp.json in your project or ~/.claude/mcp.json:

{
  "mcpServers": {
    "alltrails": {
      "command": "npx",
      "args": ["-y", "alltrails-mcp"]
    }
  }
}

Every API request routes through the fetchproxy browser bridge — it runs as a same-origin fetch inside your signed-in alltrails.com tab (DataDome fingerprints Node-originated requests, so there is no stored-cookie mode). Requirements: the ContextMint Bridge extension installed (https://github.com/nullnet-app/contextmint-bridge/releases — the fetchproxy extension renamed, same maintainer; public source, .sha256-checkable release zips; use Chrome for now), a signed-in alltrails.com tab open, and a one-time pair-code approval on first use. The x-at-key app key is never stored in code or config — it is captured live from the tab's own API traffic and held in memory only.

Tools

view — slim by default

Every tool marked view? below answers in one of two shapes, and the cheap one is what you get for free:

• view: "compact" (the default) — a slim projection of just the fields you act on. Each tool's row says exactly which.
• view: "full" — AllTrails' whole untouched record.

You do not pass anything to get the compact answer. Reach for view: "full" only when you need a field the projection drops — most often route geometry from alltrails_get_trail.