Bikepackia MCP server

Last verified September 12, 2026

Bikepackia's MCP server gives any MCP-compatible AI client four tools: planRoute, refineRoute, exportGpx and getRouteSafety. With them an agent can plan a bikepacking route from a plain-language brief, refine it with follow-up instructions, download its GPX and read its safety scorecard.

The tools

What a planned route contains

• routeId: the saved route's id. Pass it to refineRoute, exportGpx and getRouteSafety. The route is saved to your account, so the id keeps working later.
• bikeType and isEbike: the bike setup the route was planned for.
• distanceKm and ascentM: totals for the whole route.
• stages: one entry per day, with start and end coordinates, distanceKm, ascentM and a difficulty of easy, moderate or hard.
• safetyScore, safetyReview and safetyFlags: an overall 0–100 score, a short written review, and flagged stretches, each with a severity (medium or high), a reason and its length in km.

The safety scorecard is an early, advisory estimate that is still being developed. Don't rely on it for safety decisions, and don't present it to riders as a verified assessment of the roads.

Optional planning constraints

planRoute understands the brief on its own, but you can pin details with constraints. Every field is optional:

• origin, destination and isLoop: where the trip starts and ends.
• days (1–30) and dailyDistanceKm (20–250): trip length and daily distance.
• surface: road, gravel, mtb or trekking. avoidHighways defaults to true.
• waypoints: coordinates the route should pass through.
• travelers, accommodation, lunch, pace, scenery, budget and startTime: trip preferences that shape stages and stops.
• notes: anything else, as free text.

Connecting a client

The MCP server address is shared with you when access is granted. Most MCP clients take a configuration like this; the exact format depends on the client:

{
  "mcpServers": {
    "bikepackia": {
      "url": "<address provided with your access>",
      "headers": {
        "Authorization": "Bearer bpk_<your-secret>"
      }
    }
  }
}

Discovery (initialize, tools/list) works without a key. Tool calls need one. See the API keys page for authentication and limits.

Errors and long calls

• A failing tool call comes back as an MCP tool result with isError: true and a readable message, not as a transport error, so the calling model can see what went wrong and adjust.
• Planning and refining can take tens of seconds. If your client sends a progressToken, the server reports a progress notification for each planning step.
• A single planning or refining turn stops after 40 internal steps rather than running forever.
• Rate, concurrency and daily spend limits return 429. See the API keys page.

What the server doesn't do

The server offers these four route-level operations only. The fine-grained editing controls of the Bikepackia planner are not exposed. Route geometry always comes from the routing engine, never from the AI model.