Skip to main content
Glama

Related Servers

Alternatives to Elite Dangerous MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to create and optimize Elite Dangerous ship builds from natural-language goals, including engineering, constraints, hull comparisons, existing-build evaluation, and export to Coriolis, EDSY, SLEF, or journal formats.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to access live Elite Dangerous game context such as location, route, ship loadout, and journal history through local MCP tools, with an optional GitHub relay for remote access.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to read and act on EVE Online data through the ESI API, handling SSO login for multiple characters and answering in single calls with resolved names, combined requests, and locally indexed static data. Covers fittings (with attributes and EFT/DNA export), skills and skill checks, assets, market prices and orders, industry, mail, and arbitrary ESI routes.
      35
      16 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to discover and invoke read-only EVE Online ESI API endpoints, retrieve public and character data with automatic OAuth, and turn that context into practical adventure plans.
      3
      48 npm
      2
      AGPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      This MCP server provides real-time integration between Elite Dangerous and Claude Desktop, enabling AI-powered analysis of your gameplay data and dynamic generation of EDCoPilot custom content.
      3
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to search EVE Online items, validate ship fits against fitting limits, compute combat stats like DPS and EHP, and retrieve Jita market prices.
      4
      MIT

    TDQS

    C2.7/5.0

    Scored across 58 tools

    Disambiguation3/5

    The 58 tools span many distinct domains, but several station-search and analytics tools overlap in purpose, e.g. find_ship/find_module/find_commodity vs spansh_search_stations/station_services, and analyze_graph_metrics vs graph_sensitivity_analysis. Descriptions help distinguish them, but the sheer number and similar patterns create real misselection risk.

    Naming Consistency3/5

    All names use snake_case and are readable, but the convention is mixed: verb-first names (get_, find_, build_, analyze_, create_, list_) coexist with source-prefixed names (spansh_, edsm_, inara_, eddn_) and noun-only names such as system_distance and station_services. There is no single predictable pattern throughout.

    Tool Count1/5

    At 58 tools, the server is far beyond a well-scoped 3–15 tool set and exceeds the 25+ threshold where sprawl becomes a usability problem. Many tools are specialized analytics or data-source variants, making the surface feel like multiple MCP servers combined into one.

    Completeness4/5

    Coverage is broad across journal state, trade/outfitting, exploration, exobiology, colonisation, and research analytics. There are still notable gaps for a full Elite Dangerous assistant, such as missions, engineering/blueprints, combat, powerplay, and deleting/updating research records, but core data workflows are well represented.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data