mcp-tirepressure
This local MCP server provides SRAM-like bicycle tire-pressure calculations and bike-profile lookup tools.
List all configured bike profiles with tire, rim, style, and weight specs.
Retrieve a single bike profile by name.
Calculate recommended front/rear tire pressure in bar for a bike, rider weight, bike weight, and surface condition (
DRY,WET, orSNOW).Apply hookless/straight-side rim pressure caps and include explanatory notes.
Get a one-call pressure recommendation using live Open-Meteo weather from latitude/longitude coordinates, including inferred surface/weather reasoning.
Run as a FastMCP stdio server for registration with Hermes Agent.
Allows Hermes Agent to calculate recommended bicycle tire pressures using the SRAM-derived formula, including bike profiles, rider/bike weights, surface conditions, and live weather-based surface detection.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-tirepressure What's the recommended tire pressure for my BMC in Vienna today?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-tirepressure
Local MCP server (FastMCP, stdio) implementing a SRAM-like tire pressure formula as tools for the Hermes Agent.
Note: This implementation is based on the formula from the SRAM AXS Tire Pressure Calculator. The formula was reverse-engineered from the SRAM web client (August 2026). Not an official SRAM product.
Safety Notice
Important: The calculated tire pressures are recommendations based on a simplified physical formula. They do not replace the manufacturer's specifications on the tire or your own riding feel. Always check the maximum tire pressure (on the tire sidewall) and, when in doubt, increase the pressure by 0.2–0.3 bar. Use at your own risk.
Related MCP server: Training Condition Check MCP
Setup
python -m venv .venv
.venv/bin/pip install -e ".[dev]"Tools
get_bikes()— all 5 bike profilesget_bike(name)— a single bike profilecalc_pressure(bike, rider_weight, bike_weight, surface)— front/rear pressure in barget_recommended_pressure(bike, rider_weight, bike_weight, lat, lon)— with live weather
Registration in Hermes
mcp_servers:
mcp-tirepressure:
command: /path/to/mcp-tirepressure/.venv/bin/python
args: ["-m", "mcp_tirepressure"]Tool Reference
get_bikes()
Lists all 5 configured bike profiles.
Return: [{name, tire_width, inner_rim_width, wheel_diameter, ride_style, rim_type, tire_casing, bike_weight}, ...]
get_bike(name: str)
Returns a single bike profile.
Args: name — key from get_bikes() (e.g. "bmc-teamachine").
Return: profile as dict.
calc_pressure(bike, rider_weight, bike_weight, surface="DRY")
Calculates the recommended tire pressure (front/rear) in bar. Args:
bike— bike namerider_weight— rider weight in kgbike_weight— bike weight in kgsurface—"DRY","WET", or"SNOW"(default:"DRY") Return:{bike, surface, front_bar, rear_bar, notes}
get_recommended_pressure(bike, rider_weight, bike_weight, lat, lon)
One-call recommendation with live weather (Open-Meteo). Args:
bike,rider_weight,bike_weight— as abovelat,lon— coordinates (e.g. Vienna: 48.2082, 16.3738) Return:{bike, surface, weather_reason, front_bar, rear_bar, notes}
Formula
The calculation is based on the formula from the SRAM AXS Tire Pressure Calculator:
P = 10^8.6847 / C^1.3046 × (1 + (2.2 × (W_bike + W_rider) - 180) × 0.0025)
× R_pos × R_rim × R_style × R_surface × R_casing × 68.9476 × 0.001C— tire circumference in mm (derived from wheel diameter + effective width)R_pos— front/rear wheel factor (0.94 / 1.0)R_rim— rim type factor (CROCHET, STRAIGHT_SIDE, TUBES, TUBULAR)R_style— riding style factor (ROAD=1.0, GRAVEL=0.9, MTB=0.9–1.1)R_surface— surface condition (DRY=1.0, WET=0.9, SNOW=0.5)R_casing— tire casing (THIN=1.025, STANDARD=1.0, REINFORCED=0.95, DOUBLE=0.9)68.9476— PSI → bar conversion (÷ 1000)
Details: src/mcp_tirepressure/core.py
Hookless Cap
For rim_type == STRAIGHT_SIDE (hookless), pressure is capped at max
4.96 bar (72 PSI). A note in the notes field indicates whether the
cap was triggered.
Example (CLI)
.venv/bin/python -c "
from mcp_tirepressure.server import calc_pressure
import json
print(json.dumps(calc_pressure('bmc-teamachine', 93.0, 8.0, 'DRY'), indent=2))
"License
Available Tools
4 toolscalc_pressureB
Calculate recommended tire pressure (front/rear in bar) for a given bike, rider weight, and surface (DRY/WET/SNOW). Applies hookless rim cap where needed.
Inputs: bike (required), bike_weight (required), rider_weight (required), surface.
get_bikeA
Get a single bike profile by name. Returns specs + bike weight.
Inputs: name (required).
get_bikesA
List all configured bike profiles (name, tire/rim specs, style).
Inputs: no named parameters. Returns: result
get_recommended_pressureB
One-call recommended pressure with live weather. Fetches Open-Meteo data, determines wet/dry, and returns front/rear pressure in bar.
Inputs: lat (required), lon (required), bike (required), bike_weight (required), +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
get_bikes and get_bike are clearly distinct list-vs-detail tools, but calc_pressure and get_recommended_pressure overlap noticeably. Both return front/rear pressure recommendations; the key difference is explicit surface vs live weather, which is described but could still cause selection ambiguity.
Tool names mostly follow a get_/calc_ verb_noun pattern, and the get_bikes/get_bike pair is nicely consistent. calc_pressure uses an abbreviation rather than calculate_pressure and get_recommended_pressure includes an adjective, so there are minor deviations but no chaotic mixing.
Four tools is well-scoped for a niche tire-pressure server with no bloat or obvious excess. Each tool has a distinct role in listing bikes, retrieving bike details, manual calculation, and weather-driven recommendation.
The core workflow of retrieving bike profiles and getting pressure recommendations is covered, including both manual surface input and live weather. The main gap is the lack of bike profile creation/update/delete, though profiles may be externally configured.
Maintenance
Related MCP Connectors
AI cycling coach: training plans, workouts, nutrition, strength training, Strava, Garmin and Wahoo.
Weather MCP — wraps Open-Meteo API (free, no auth)
Forecasts for any US point, with context: alerts, what changed overnight, why, and history.
Create structured workouts and push them to Apple Watch or Garmin.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceProvides real-time weather data and forecasts for any location using the OpenWeatherMap API. Supports current weather conditions, 5-day forecasts, and weather alerts with optional demo data when no API key is configured.-
- AlicenseNot gradedqualityDmaintenanceProvides personalized recommendations for optimal outdoor exercise times by integrating weather data, Garmin Connect training schedules, and user performance metrics.3Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables natural language queries about Ambient Weather personal weather station data, including current conditions and device info.MIT
- FlicenseBqualityDmaintenanceProvides weather forecasts and active alerts from the US National Weather Service API for US locations.2-