The AI Engine that turns raw geodata into Predictive Intel.
Plan with certainty and scout the terrain before you ride: analyze soil drainage, wind vectors, and technical grade before you drop in.
BikeScout isn't just a map tool; it's a Tactical Intelligence Engine. It transforms static geographical data (OSM) into actionable insights by simulating real-world physics, weather history, and technical terrain difficulty.
Whether you are planning a gravel expedition or an E-MTB mission, BikeScout calculates the "hidden variables" that generic navigators ignore.
The Model Context Protocol (MCP) is an open standard that allows AI agents (like Claude, ChatGPT or Ollama) to use external tools safely and efficiently.
By running BikeScout as an MCP server, you give your AI the "eyes" to see trails, "hands" to generate GPX files, and the "brain" to analyze soil conditions, turning a simple LLM into a professional cycling scout.
Bridging the gap between maps and reality.
Predicting the unpredictable.
Precision routing for AI agents.
Energy management for man and machine.
Standard navigation tools like Google Maps or Komoot are designed for simple "lines on a map." BikeScout is built for Mission Planning, bridging the gap between raw data and technical reality.
| Feature | Generic Navigators | BikeScout Tactical AI |
|---|---|---|
| Elevation Accuracy | Raw & Inflated | Filtered & Realistic (SMA) |
| Surface Analysis | Basic (Paved/Dirt) | Technical (S-Scale/Tracktype) |
| Effort Calculation | Time-based average | Physics-based (Weight/Friction) |
| Condition Prediction | Future Weather only | Mud Risk (72h Rain + Soil Memory) |
| Climb Categorization | None | UCI-Standard (Cat 4 to HC) |
| Logistics | Sponsored / Restaurants | Tactical (Water/Repair/Shelter) |
| AI Integration | Manual / External | Native MCP Tooling |
Follow these sections to deploy BikeScout in your environment.
Pre-Requirements:
To integrate BikeScout with your preferred MCP client (e.g. Claude Desktop, Cursor, Google Antigravity), add the following configuration to your settings file:
Add the server to your MCP client config file:
.claude/settings.json
.cursor/mcp.json
.gemini/antigravity/mcp_config.json
.codex/config.toml
.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"bikescout": {
"command": "PATH/TO/YOUR/PYTHON_VENV",
"args": ["-u", "-m", "bikescout.mcp_server"],
"env": {
"PYTHONPATH": "PATH/TO/SRC",
"ORS_API_KEY": "YOUR_KEY"
}
}
}
}
Pre-Requirements:
To integrate BikeScout Skills with your preferred MCP client (e.g. Claude Desktop, Cursor, Google Antigravity), follow these steps:
Add the .agents/skills folder in the following locations:
~/.agents/skills
~/.gemini/antigravity/skills
~/.agents/skills
Pre-Requirements:
.env.example to .env and paste keys:
If you prefer a private and free experience without external API costs.
Pre-Requirements:
.env.example to .env and paste keys:
To integrate the MCP tools within the Open WebUI interface, follow these steps:
| Field | Tactical Value |
|---|---|
| Type | OpenAPI |
| URL | http://mcpo:8000/bikescout |
| OpenAPI Spec | Set to URL and use openapi.json |
| Auth | None |
| ID / Name | bikescout |
Once saved, you can enable this tool for your specific models in the New Chat, Workspace or Model settings, allowing the LLM to access real-time data through your MCP server.
You can test BikeScout using the MCP Inspector, a web-based tool for testing MCP servers. To launch the inspector and interact with the tools manually, run the following command from the root directory:
Run the test suite with pytest:
python -m pytest
python -m pytest --cov=src/bikescout --cov-report=term-missing
Note: Local tests are executed using the virtual environment's Python interpreter to ensure dependency alignment with the production MCP server.