MCP server

Claude, Cursor and any other client that speaks the Model Context Protocol can call the same computations as the REST API, without you writing an integration.

Endpoint: https://thirdtrail.life/mcp
Transport: Streamable HTTP (JSON-RPC 2.0)
Protocol: MCP 2026-07-28 (stateless), plus 2025-03-26 through 2025-11-25 for older clients
Availability: calling tools needs a paid plan (see pricing). Anyone can list the tools.

Connecting

Authenticate with the same API key you use for REST, sent as a bearer token. You can create one in your dashboard.

claude mcp add --transport http thirdtrail https://thirdtrail.life/mcp \
  --header "Authorization: Bearer tt_live_xxxxx"

If your client is configured with a file, add this entry:

{
  "mcpServers": {
    "thirdtrail": {
      "url": "https://thirdtrail.life/mcp",
      "headers": { "Authorization": "Bearer tt_live_xxxxx" }
    }
  }
}

What tools you get

Each API key belongs to one subscription, and so to one API. The server lists only the tools that key can call, so a session never offers a tool that would fail.

Without a key, the server lists every tool below, so you can see what is on offer before subscribing. Calling any of them needs a paid key.

  • Ephemerides: get_sun_moon_times, get_prayer_times
  • Solar: get_solar_position, get_solar_path, get_daily_light_integral
  • Tides: get_tide_extremes, get_tide_heights, get_tide_window

Subscribed to more than one API? Add the server once per key, under a different name each time.

Elevation

Every tool that computes the sun or moon takes an optional elevation in metres, and the tool descriptions tell the model to pass it whenever it knows it. A sea-level sunrise is the wrong answer at altitude, and most tools an agent can reach have no way to ask for anything else.

That includes get_tide_window, whose sun, moon and golden-hour values come from the same engine as the Ephemerides API. On a clifftop, where coastal photographers often stand, elevation moves those times by about three minutes.

get_tide_extremes and get_tide_heights do not take an elevation. How high the water rises has nothing to do with how high you are standing, so those two tools have no elevation parameter.

Limits and billing

Tool calls count against your plan the same way REST calls do, with the same limits: a days value beyond your plan's horizon is refused with the same message. Connecting and listing tools are not billed.

Informational use only, not for navigation or life-safety decisions. See safe use.