Skip to main content
Glama
mcp-tirepressure

mcp-tirepressure

by StefanOOEOrg

mcp-tirepressure

CI M8ven Score

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 profiles

  • get_bike(name) — a single bike profile

  • calc_pressure(bike, rider_weight, bike_weight, surface) — front/rear pressure in bar

  • get_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 name

  • rider_weight — rider weight in kg

  • bike_weight — bike weight in kg

  • surface — "DRY", "WET", or "SNOW" (default: "DRY") Return: {bike, surface, front_bar, rear_bar, notes}

One-call recommendation with live weather (Open-Meteo). Args:

  • bike, rider_weight, bike_weight — as above

  • lat, 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.001
  • C — 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

MIT

Available Tools

4 tools
calc_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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 4 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers