Skip to main content
Glama
dragosh29

AppyWay MCP server

by dragosh29
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to AppyWay MCP server

No user-submitted related servers found.

    Related Servers

    • parknyc-mcp

      ltyu
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables managing NYC parking sessions, vehicles, and zones through MCP clients using the ParkNYC/Flowbird API.
      -

    • Appointedd MCP Server

      dragosh29
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to search availability, read services, resources, bookings and customers, and, when writes are enabled, reserve slots, create or cancel bookings, and add or update customers.
      10
      MIT

    • Spoke Dispatch MCP server

      dragosh29
      A
      license
      A
      quality
      C
      maintenance
      Lets MCP clients read a delivery route planning and driver dispatch team's plans, stops, routes, drivers, depots, and optimization operations, and when writes are enabled, create plans, import stops, optimize routes, and distribute them.
      12
      MIT

    • ultimate-travel-agent

      Gustor1
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to access 21 read-only tools for local travel planning, including trip and itinerary validation, budget calculation, booking requirements, integration provider status, flight/train/accommodation/activity searches, route/weather/currency lookups, and travel source search.
      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.9/5.0

    Scored across 8 tools

    Disambiguation4/5

    Tools target distinct resources (area rules, kerb map, entity, zone, authorities, reference data) and descriptions actively cross-reference each other (e.g. fetch_kerb_segments tells you to use find_parking_rules_near for prices). Minor overlap remains between find_parking_rules_near and fetch_kerb_segments since both take an area and return parking entities, and get_parking_entity vs fetch_kerb_segments both return entity details.

    Naming Consistency4/5

    Strong verb_noun convention throughout (find_parking_rules_near, fetch_kerb_segments, get_parking_entity, get_zone_rules, list_authorities, get_authority_restrictions, list_reference_values). Only 'ping' deviates, which is a minor and understandable exception for a health-check tool.

    Tool Count5/5

    Eight tools is well-scoped for a read-only parking data API, with each tool earning its place (health check, two area queries, two entity/zone lookups, authority queries, reference data). No redundant or filler tools.

    Completeness4/5

    Covers the main lifecycle for querying parking data: accessibility check, area search, entity/zone lookup, authority discovery and restrictions, and reference ids. Gaps are minor (e.g. no explicit address/geocode search or pagination handling), but agents can work around these via the provided area and id-based tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources