AdisInsight
Query Springer Nature's drug-pipeline and trial database from an AI agent.
Search AllTrails' trails by place, map bounds or name and pull details and a 7-day trailhead forecast from your AI…
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The AllTrails MCP server connects AllTrails' trail catalogue to Claude, ChatGPT and any MCP-compatible agent. Its 5 read-only tools search trails near a point, inside map bounds or by name, return a trail's description, difficulty, stats and review summary, and give a seven-day forecast at the trailhead. No account, key or sign-in is needed.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Find hiking, running, biking, backpacking or other trails for outdoor activities near a set of coordinates within an optional specified maximum radius (meters). Use this tool when the user: * Requests trails near a specific point of interest or landmark. * Requests trails near a named location within a specified radius or accessible within a specified time constraint. * Provides specific latitude and longitude coordinates. For most named places, use the "search within bounding box" tool if possible. Use this tool as a fallback when the bounding box of the named place is unknown. Users can specify filters related to appropriate activities, attractions, suitability, and more. Numeric range filters related to distance, elevation, and length are also available. These filter values MUST be specified in meters. In the response, length and distance values are returned both in meters and imperial units. These MUST be displayed to the user in the units most appropriate for the user's locale, e.g. feet or miles for US English users.
Find hiking, running, biking, backpacking or other trails for outdoor activities within a specified bounding box defined by southwest and northeast coordinates. Use this tool when the user: * Requests trails within specific geographic boundaries or coordinates. * Requests trails near a named geographic or political place, such as a continent, country, state, province, region, city, town, or neighborhood and you know the bounding box for that place. * Requests trails within a national, state or local park or other protected area and you know the bounding box for that park. If the bounding box for the named place is not known, use the "find trails near a location" tool instead to find trails around a center point. Users can specify filters related to appropriate activities, attractions, suitability, and more. Numeric range filters related to distance, elevation, and length are also available. These filter values MUST be specified in meters. In the response, length and distance values are returned both in meters and imperial units. These MUST be displayed to the user in the units most appropriate for the user's locale, e.g. feet or miles for US English users.
Search for hiking, running, biking, backpacking or other trails by full or partial name match. Use this tool when the user: * Requests a specific trail by name (e.g., "Avalanche Lake Trail", "Half Dome") * Searches for trails with specific keywords in the name The search can biased towards results near the provided coordinates if they are provided explicitly or available from the request metadata. If there is a clear match to the user's query, the model should automatically make a subsequent call to the `get_trail_details` tool to present the user with complete details for the matching trail. In the response, length and distance values are returned both in meters and imperial units. These MUST be displayed to the user in the units most appropriate for the user's locale, e.g. feet or miles for US English users.
Find detailed information about a trail from AllTrails. Get descriptive overviews and specific accessibility information. Includes structured data about suitable activities, and feature highlights along the trail. Get stats about the trail geography and length, and stats about associated user-generated content. In the response, length and distance values are returned both in meters and imperial units. These MUST be displayed to the user in the units most appropriate for the user's locale, e.g. feet or miles for US English users. Recent reviews are summarized in the `review_summary` field. If the user wants information that might be found in specific reviews, direct the user to the AllTrails web URL for the trail.
Get 7-day forecast for a trail at its trailhead, including high/low temperatures. For more detailed weather information, including current conditions, sunrise/sunset times, and weather alerts, direct the user to the AllTrails web URL for the trail (available in the `get_trail_details` tool response).
Read from the server on 2026-08-18, including each tool's own safety annotations.
tools/list, so that path ends in the AllTrails app.get_trail_details returns a summary of recent reviews and a profile photo URL; individual reviews, photo galleries and the GPX track are not exposed, and the tool directs users to the trail's web page for review detail.initialize, tools/list, prompts/list, prompts/get, resources/list, resources/templates/list and one resources/read of a widget. Everything above comes from those responses, from the schemas, and from AllTrails' own published pages — not from calling a search.No. AllTrails' support article states that no API keys, accounts or additional configuration are required. We confirmed it on 2026-08-18: an anonymous handshake against the endpoint returned all five tool schemas with no credential and no authentication challenge. Nothing on the server reads or writes an AllTrails account, so a free reader and a subscriber get the same five tools.
No. The five tools the live server exposes only read the catalogue. Its own prompt names create_list, add_trails_to_list and get_lists and offers to save results, but none of those three appear in tools/list, so an agent that accepts the offer has nothing to call. Saving, favouriting and trip planning stay in the AllTrails app.
Treat it as catalogue data, not a safety assessment. Difficulty comes back as one of three AllTrails labels — easy, moderate or hard — describing the trail as catalogued, never your fitness, gear or the conditions on the day. AllTrails' terms disclaim any warranty of accuracy, completeness or suitability and state that real-world conditions may differ from what the product shows.
It is a seven-day forecast of high and low temperatures at the trailhead, plus an optional alert string. That is all the output schema carries. The tool itself tells the agent to send you to the trail's AllTrails page for current conditions, sunrise and sunset times, and full weather alerts, so the connector is a planning glance rather than a conditions check before you set out.
Because they govern different things. The robots file at alltrails.com disallows ClaudeBot, Claude-User, Claude-SearchBot and GPTBot from the trail catalogue, then names a short allowlist of marketing paths such as /about and /press. The MCP server on the same host answers anonymously. AllTrails is declining open crawling of its catalogue and offering a defined tool surface instead.
No. The server publishes two HTML widget resources — a pin map with swipeable cards and a trail detail card — and only clients implementing the MCP Apps UI extension draw them. Elsewhere the connector degrades to text, which is why the widget descriptions instruct the agent to summarise results in chat alongside the widget rather than relying on it.
Nineteen activities, from hiking, trail running and mountain biking through backpacking, snowshoeing and via ferrata, per the live search schemas. You can also filter on fifteen attractions such as waterfalls, lakes and wildflowers, eight suitability flags including dog and stroller access, three difficulty levels, three traffic levels, route type, rating, length, duration and elevation.
…-AI-services; the canonical article slug is …-AI-assistants. And the HTML route returns HTTP 403 to an automated client while support.alltrails.com/robots.txt permits /hc/en-us/articles/, so the body was read through the public Zendesk Help Center API at /api/v2/help_center/en-us/articles/47343827423764.json (HTTP 200) — a bot block, not a policy refusal. · retrieved 2026-08-18initialize against https://www.alltrails.com/mcp (2026-08-18, HTTP 200) — protocol 2025-06-18, serverInfo name "AllTrails MCP Server" version 1.27.0, declaring prompts, resources and tools capabilities. Answered an anonymous request with no credential and no challenge; this is what sets authVerified · retrieved 2026-08-18tools/list handshake against the same endpoint (2026-08-18) — 5 tools with titles, descriptions, input and output schemas, _meta blocks and safety annotations, returned to an unauthenticated client. Source for every tool name, annotation state, filter enum, cap and parameter shape quoted above. Schemas committed at docs/marketing/data/tool-schemas/alltrails.tools.json · retrieved 2026-08-18prompts/list and prompts/get against the same endpoint (2026-08-18) — one prompt, search_trails_assistant, whose description and body name three tools absent from tools/list · retrieved 2026-08-18resources/list, resources/templates/list and resources/read against the same endpoint (2026-08-18) — two text/html;profile=mcp-app widget resources with _meta.ui CSP blocks and OpenAI vendor metadata keys; the template list is empty · retrieved 2026-08-18https://www.alltrails.com/robots.txt (retrieved 2026-08-18, HTTP 200) — names ClaudeBot, Claude-User, Claude-SearchBot, ChatGPT-User, GPTBot, OAI-SearchBot, CCBot, PerplexityBot, Google-Extended, Applebot-Extended and Meta-ExternalAgent. Each appears in two groups: a Disallow: / group, and a later group allowing a named set of marketing paths (/$, /about*, /press*, /plans*, /newsroom* and a few others). So the trail catalogue is closed to these agents while a small brand surface stays open — not a blanket site-wide block, and reading only the first group would overstate it. The file carries no Content-Signal line. Nothing on this page is synthesised from www.alltrails.com page content; the prose above is built from the live MCP handshake, the terms page and the Zendesk support article. https://www.alltrails.com/llms.txt returns 403 and https://support.alltrails.com/llms.txt returns 404, so no machine doc index exists · retrieved 2026-08-18Connect AllTrails once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.