Skip to main content
Glama
ESGO-Logistics

ESGO MCP Server

Official
by ESGO-Logistics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ESGO MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • bolsa-de-carga-mcp

      cargoffer
      A
      license
      Not graded
      quality
      D
      maintenance
      Freight marketplace MCP server for European road logistics. Search and manage freight loads, post truck capacity, create auctions, manage deliveries and drivers through the Cargoffer Bolsa de Carga API. Connect your AI agent to the freight marketplace.
      1
      MIT

    • LogiSwarm AI MCP Server

      devcrazy2812
      A
      license
      A
      quality
      B
      maintenance
      Enables autonomous multi-agent logistics operations through MCP tools, resources, and prompts for routing, inventory, cargo inspection, disruption recovery, and conversational dispatch. It supports both modern and legacy MCP specs over stdio and HTTP, including secure API and feedback-optimized workflows.
      5
      1
      MIT

    • CargoEffe MCP Server

      dollob
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to CargoEffe for automated cargo loading plan design, offering tools to manage containers, cargo items, and load plans.
      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 4 tools

    Disambiguation4/5

    matches_search and open_requests_list_matches both concern 'matches', which could cause some initial confusion, but the descriptions clearly separate proactive capacity search from listing matches of an existing request. me_retrieve and open_requests_create are unambiguous.

    Naming Consistency4/5

    All names follow a consistent snake_case resource_action pattern (matches_search, open_requests_create, open_requests_list_matches, me_retrieve). Minor deviation: 'me_retrieve' and the compound action 'list_matches' break the clean resource_verb rhythm slightly, but the convention is still predictable.

    Tool Count4/5

    Four tools is a lean but coherent set for a focused transport-matching API, covering auth check, capacity search, request creation, and match retrieval. It's on the thin side but each tool earns its place with no obvious filler.

    Completeness3/5

    The surface covers search, create, and match-listing, but there is no way to list one's own open requests, retrieve a single request, or update/cancel an existing request. These are notable lifecycle gaps for a request-management domain, though core workflows are usable.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources