The catalogue, as data

Endpoints

• GET /api/v1/spotsEvery spot with planning facts. ?q= for free-text search.
• GET /api/v1/spots/{slug}One spot in full. ?geometry=1 adds the profile and trail line.
• GET /api/v1/regionsRegions with counts and offline pack URLs.
• GET /spots/{slug}/gpxThe trail as GPX 1.1 — attribution inside the file.
• GET /regions/{slug}/packThe region as one GeoJSON FeatureCollection.
• POST /api/mcpThe MCP server (Streamable HTTP, JSON-RPC 2.0).

The MCP server

Point any MCP client at the endpoint below and it gets three read-only tools: search_spots, get_spot and list_regions — the same catalogue the site serves, with the same honesty rules baked into the responses.

{
  "mcpServers": {
    "hikespot": {
      "type": "http",
      "url": "https://hikespot.com/api/mcp"
    }
  }
}

Terms, short version

• Trail geometry is © OpenStreetMap contributors under ODbL 1.0 — keep the attribution, share derived geodata alike. Elevation is USGS 3DEP, public domain.
• Condition data is dated hiker observation, never authority. If you redistribute it, keep the dates and the disclaimer.
• Protected coordinates are generalized at the source. Don’t try to reconstruct them; the land managers asked.
• No SLA. Cache for at least five minutes; the data changes slowly.