Skip to main content
Glama
RobsonAdvincula

fleetsync-mcp

by RobsonAdvincula
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to fleetsync-mcp

No user-submitted related servers found.

    Related Servers

    • UPS MCP Server

      VoxveyAI
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to track packages, rate and create shipments, manage pickups and customs documentation, and perform international shipping logistics checks through natural language.
      MIT
    • Easyship MCP by easyship

      Easyship MCPofficial

      easyship
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI agents to manage global shipping operations, including rate comparison, shipment creation, label purchasing, tracking, pickup scheduling, address validation, billing, and analytics, via natural language.
      6 npm
      MIT

    • ILP Drone Delivery MCP Server

      RheaBose
      F
      license
      A
      quality
      D
      maintenance
      Enables Large Language Models to interact with the ILP Drone Delivery System to plan deliveries, check drone availability, and generate route visualizations. It allows users to manage logistics tasks like capacity planning and temperature requirement matching through natural language.
      6
      -

    • logistics-mcp

      Azzaraell
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to query and manage logistics shipment data, supporting operations like tracking, quoting, and performance analysis via nine tools backed by a demo dataset or a REST API.
      9
      253 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.6/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools are clearly distinct, but the overlapping query tools (orders_by_date vs orders_by_route_date, get_routes vs routes_by_date) could cause misselection if an agent doesn't read descriptions carefully. Each tool has a unique filter or aggregation purpose, so ambiguity is low but not absent.

    Naming Consistency3/5

    All tools share the fleetsync_ prefix, but the verb_noun pattern is broken by query-style names like orders_by_date, orders_status_changes, order_history, and routes_by_date. This mixed convention reduces predictability, though the domain terms keep the names readable.

    Tool Count4/5

    At 18 tools, the set is slightly over the ideal 3-15 range, but the count is justified by full CRUD for both orders and routes plus multiple query views and an analytics tool. Each tool has a clear purpose, so it feels slightly heavy rather than bloated.

    Completeness3/5

    The set covers CRUD for orders and routes, along with useful queries and distance analysis. However, order status cannot be updated (only read), route status is not manageable, and driver tools are limited to listing. This leaves significant gaps for agents needing to update delivery progress or assignments.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources