Elite Dangerous MCP
Related Servers
Alternatives to Elite Dangerous MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables 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.1MIT
- AlicenseAqualityBmaintenanceEnables 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.3512 npmMIT
- AlicenseAqualityBmaintenanceEnables 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.331 npm2AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceThis 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.3MIT
- AlicenseAqualityBmaintenanceEnables 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.4MIT
- AlicenseNot gradedqualityDmaintenanceConnects LLM agents to live and simulated satellite telemetry, NOAA space weather data, and space debris orbital conjunction analysis.MIT
TDQS
Scored across 12 tools
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.
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.
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.
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.