Bikescout MCP Server

BikeScout is a specialized AI engine for MTB, Road, E-Bike, and Gravel mission planning. It transforms raw map data into Tactical Intelligence, predicting terrain conditions and trail hazards. The system provides precise setup advice. The bikescout mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.

What it actually does

• Transparency: Any modified version of BikeScout used to provide a service over a network (SaaS/Cloud) must make its full source code available to the community
• Integrity: The core tactical intelligence remains open and collaborative, preventing "closed-source" commercial hijacking of the platform's unique algorithms

Its toolset

Everything the assistant can do here goes through one of these:

• Transparency — Any modified version of BikeScout used to provide a service over a network (SaaS/Cloud) must make its full source code available to the community
• Integrity — The core tactical intelligence remains open and collaborative, preventing "closed-source" commercial hijacking of the platform's unique algorithms
• Platform — What they provide
• Komoot — Static maps
• Strava — History/Social
• Trailforks — Databases

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Bikescout's toolset — Transparency, Integrity, Platform and 3 more — is a fair guide to whether it matches your workflow. It is maintained by hifly81; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the bikescout mcp server does with a few real requests.