Skip to main content
Glama
ramgarden

Elite Dangerous MCP

by ramgarden
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Elite Dangerous MCP

No user-submitted related servers found.

    Related Servers

    • SpaceOps Satellite Operations

      jdbruh18
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects LLM agents to live and simulated satellite telemetry, NOAA space weather data, and space debris orbital conjunction analysis.
      MIT

    • mcp-jpl-ssd

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query NASA/JPL data on asteroids and comets, including small-body orbits and physical parameters, near-Earth close approaches, Sentry impact-risk assessments, and recent atmospheric fireballs. All four tools are keyless and work over a hosted gateway endpoint or a local stdio server.
      65 npm
      MIT

    • Yamcs MCP Server

      PaulMRamirez
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to interact with Yamcs mission control systems through natural language, providing tools and resources for telemetry, commands, links, storage, instances, and alarms.
      34
      4
      MIT

    • mcp-engram

      shuruheel
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables LLMs to build and explore a cognitive neuroscience-inspired knowledge graph with SQLite, supporting search, graph traversal, temporal sequences, and structured reasoning.
      24
      MIT

    • Calibre MCP Server

      Miguel0888
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI agents with research capabilities for local Calibre e-book libraries, including fulltext search across titles, ISBNs, and comments, plus structured excerpt retrieval from books.
      2
      GPL 3.0
    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

    B3.1/5.0

    Scored across 12 tools

    Disambiguation3/5

    Several tools retrieve similar data from different providers (e.g., inara_search_nearest vs spansh_find_nearby_stations vs edsm_sphere_systems; get_commander_status vs get_current_location), so an agent may need descriptions to choose correctly. Core distinctions exist by provider/granularity, but overlap remains.

    Naming Consistency4/5

    All names are snake_case and follow recognizable source/action prefixes: get_* for local journal tools, provider_* for external API calls, and verb_noun for composite tools. Minor deviations like edsm_sphere_systems (noun phrase) and find_colonisation_candidates (no source prefix) keep it from perfect consistency.

    Tool Count5/5

    12 tools is well within the ideal 3-15 range and each tool maps to a distinct data source or workflow (local journals, EDSM, Spansh, Inara, EDDN, colonisation, shopping list). No tool feels like filler.

    Completeness4/5

    The surface covers the apparent colonisation/shopping/status domain well, including candidate finding, system assessment, and shopping-list generation. Minor gaps exist for standalone station market/outfitting or shipyard queries, but agents can work around them via existing external-search tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources