Skip to main content
Glama
nhannpl

Winnipeg City MCP Server

by nhannpl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Winnipeg City MCP Server

No user-submitted related servers found.

    Related Servers

    • data-winnipeg by pipeworx-io

      data-winnipegofficial

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching and querying Winnipeg Open Data datasets through natural language or SoQL, with tools for datasets, metadata, and row-level data.
      6 npm
      MIT

    • transit-mcp

      aminamos
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to access real-time and scheduled public transit data, including routes, stops, departures, and service alerts, across multiple US metropolitan areas.
      5
      MIT

    • OC Transpo MCP Server

      dwdraju
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time transit data for OC Transpo in Ottawa, including live vehicle positions and trip updates via GTFS-RT feeds. It enables AI agents to monitor arrival delays, schedule changes, and transit telemetry through the Model Context Protocol.
      2
      -

    • data-calgary

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying Calgary open data from data.calgary.ca using the Socrata SODA API through natural language questions or direct tool calls.
      6 npm
      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.5/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have distinct purposes, but 'plan_journey', 'plan_timed_itinerary', and 'plan_trip' could cause confusion due to overlapping trip-planning functionality. Their descriptions clarify differences (multi-stop vs. timed itinerary vs. point-to-point), but an agent might initially misselect without careful reading.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun pattern throughout (e.g., 'find_stops_near', 'get_bus_arrivals'), with only minor deviations like 'plan_timed_itinerary' being slightly longer. The naming is predictable and readable, supporting easy identification.

    Tool Count5/5

    With 8 tools, the count is well-scoped for a city transit and services server. Each tool addresses a specific aspect of Winnipeg's public services (e.g., transit stops, arrivals, journeys, neighborhoods, 311 issues), avoiding bloat while covering core functionalities.

    Completeness4/5

    The toolset provides strong coverage for transit planning, real-time arrivals, and neighborhood/311 services, with no major gaps in core workflows. Minor gaps might include lack of tools for transit alerts or detailed neighborhood demographics, but agents can work effectively with the available tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources