Alltrails MCP Server

What srinath1510/alltrails-mcp-server MCP server does

The srinath1510/alltrails-mcp-server MCP server was created to expose selected AllTrails data through the Model Context Protocol. Its intended use was trail discovery and lookup for hiking-related questions, especially trails located within a specified national park.

The project defined two tools:

• search_trails searched for trails associated with a national park. It expected a park slug in a format such as us/tennessee/great-smoky-mountains-national-park.
• get_trail_details looked up a particular trail using the slug taken from an AllTrails URL.

The original documentation described trail information such as difficulty, length, elevation gain, descriptions, ratings, route types, and summaries. Those capabilities are historical only. The srinath1510/alltrails-mcp-server MCP server is deprecated, archived, and no longer functional.

How it works

The srinath1510/alltrails-mcp-server MCP server was implemented as a local Python process communicating over standard input and output. The README identified MCP tool support and listed protocol version 1.9.4, with a server name of alltrails-mcp and version 0.1.0.

A compatible MCP client could launch the process and call the search or detail tool. The README specifically documented Claude Desktop configuration and stated that other MCP-compatible clients could use the standard protocol. Example requests included finding trails in Yosemite or retrieving a trail by its AllTrails slug.

That operating model no longer provides usable AllTrails results. The repository states that scraping was disabled after AllTrails raised concerns about unauthorized scraping, data extraction, intellectual property, and redistribution of copyrighted content.

Setup and configuration

Historical setup required Python, a cloned copy of the repository, and dependencies installed from requirements.txt. The README described both virtual-environment and system-Python workflows. It also documented a Docker build using the local image name alltrails-mcp and a stdio configuration for Claude Desktop.

The documented process command was python3 server.py. Claude Desktop examples used either the Python executable from a virtual environment or python3 with the project’s server.py path. These instructions are retained as historical reference only and should not be treated as a way to restore functionality.

The repository’s prerequisites mentioned Python 3.8 or later, macOS testing, and other Unix-like systems. The badge identifies Python 3.10 or later, so the source material contains differing Python-version references.

Limitations and notes

The srinath1510/alltrails-mcp-server MCP server should not be selected for a production integration or current trail search workflow. The project was explicitly marked deprecated and archived on January 25, 2026, and the README says that it no longer works.

No official AllTrails API access is included in the repository. The stated alternatives are to use the official AllTrails website or contact AllTrails directly about API access. Any replacement should also respect AllTrails’ terms of service and applicable copyright restrictions.