Winnipeg City MCP Server

Smart Commute: Get bus arrivals combined with current weather conditions.
Helpful for deciding if you need a parka or just a light jacket while waiting.

Search for bus stops near a specific geographic coordinate.
Useful when you know the location (e.g. from a user's known lat/lon) but need stop IDs.

NOTE: Distance is capped at 2000 meters to allow efficient querying.

Plan a trip between two points using Winnipeg Transit.

Arguments 'origin' and 'destination' can be:
- Plain text addresses or landmarks (e.g. "The Forks", "IKEA", "123 Main St") - Resolved via OSM
- Stop numbers (e.g. "10625", "Stop 10541")
- Formatted keys:
    - "stops/{key}"
    - "geo/{lat},{lon}"
    - "intersection/{key}"

Plan a multi-stop journey (A -> B -> C ...).

Args:
    stops: List of locations (plain text, stop numbers, or formatted keys)
    optimize: If True, optimized the visit order (TSP) starting from the first stop.
    date: Optional start date (YYYY-MM-DD or equivalent accepted by API).
    time: Optional start time (HH:MM).

Plan an optimized itinerary with specific stay durations at each stop.

Args:
    stops_config: List of dictionaries. The first stop is the origin.
        Each item format: {"location": "...", "min_stay": minutes, "max_stay": minutes}
        (Stay times for the LAST stop are ignored).
    start_date: YYYY-MM-DD
    start_time: HH:MM

Get a list of Winnipeg neighborhoods that have had recent 311 activity.
Optionally filter by a search_term (e.g., 'Fort').