Skip to main content
Glama
Sign In
MCP Weather & Transit Advisor

MCP Weather & Transit Advisor

by viaanshetty3-debug
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to MCP Weather & Transit Advisor

No user-submitted related servers found.

    Related Servers

    • Live Transit MCP Server

      loama
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to query live public transport status, alerts, line maps and vehicle positions across worldwide networks through tools such as search, network_status, line_status, disruptions, airport and vehicles_near.
      MIT

    • SF Bay Area Transit MCP

      czekaj
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to find Bay Area places and stops and plan complete door-to-door journeys — walking legs, transit routes, transfers, and departure/arrival times, including deadlines and comparisons with walking or cycling — without API keys or authentication. Results come as readable itineraries plus structured data, with an interactive itinerary widget in supporting clients.
      1
      MIT

    • open-meteo

      Jose24San
      A
      license
      A
      quality
      C
      maintenance
      Enables users to geocode city names and retrieve current weather conditions plus a 1–7 day forecast through a public weather API, with no API key required, for MCP clients such as Claude Desktop or Cursor.
      2
      MIT

    • ttc-mcp

      LunaParker
      A
      license
      A
      quality
      B
      maintenance
      Enables Claude and other MCP clients to answer live questions about Toronto's transit network, including next arrivals, routes, connections, detours, accessibility and service advisories. It fetches TTC timetables and real-time feeds on demand, reporting data freshness and attaching relevant disruptions to each answer.
      19
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action: coordinate lookup, current conditions, end-to-end commute planning, and stop-level departures. The two transit tools are clearly separated by scope (trip planning vs. a single stop's board), and geocode_location is explicitly a coordinate helper rather than a weather query.

    Naming Consistency5/5

    All four names are snake_case verb_noun constructions (geocode_location, get_current_weather, get_commute_advice, get_stop_departures), with a consistent get_ prefix on the retrieval tools. No mixing of camelCase or vague single-word verbs.

    Tool Count4/5

    Four tools is on the thin side but each one earns its place in a small weather+transit surface, with no filler or redundant tools. A forecast tool would round it out, but the count is well-scoped for the stated purpose.

    Completeness3/5

    Core workflows exist, but the weather side stops at 'current' with no forecast/hourly outlook, and commute advice is fixed to 'leaving now' with no departure-time or alternative-route parameter. There is also no reverse geocoding, leaving notable gaps for a server billed as a weather and transit advisor.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Resources