All servers / Gaming / Elite Dangerous MCP server
Elite Dangerous MCP server
MCP server for Elite Dangerous build planning: Inara, EDSM, Frontier CAPI and Spansh tools for Claude
Tested by ConnectATDScore 80 out of 100. Tested 2026-11-19 on package version 0.7.1. Package: ed-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 14 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (1.2 seconds including download)
- Tools offered: 51
- Last published: 2026-11-17
- Weekly downloads (npm): 936
- License: MIT · Direct dependencies: 0
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
cache_refresh0 of 1 parameter describedClear cached data so the next call fetches fresh data. source: a source name or 'all' (default). For 'catalog' and 'ships' this also checks upstream for new game data.
cache_statusno parametersShow cached entries and their age per source, and the catalog and ship data versions.
plan_listno parametersList saved plans with item counts, progress and next_stop (the first stop still to do). A plan is a ship build or a route, or both.
plan_get0 of 1 parameter describedGet a saved plan (a build or a route) by id. next_stop is the first stop still to do, in the saved route's order when there is one, else in the order of stops.
plan_upsert0 of 1 parameter describedCreate or replace a plan. A plan is a ship build, a route, or both: for example system X, planet Y for bios, then planet Z, then station A to hand in. Items are things to buy, engineer, unlock, gather or trade, plus refits (moving modules between slots, storing modules, or a fitting decision). Stops are the places to visit, each with a system and optionally a station or body (planet or moon), a label, a kind, a status (todo, done, skipped), notes and after rules. Without a saved route, the order of stops is the visiting order; route is the order route_stops saved. Replacing keeps created_at.
plan_update_item0 of 4 parameters describedSet the status and/or notes of one plan item.
plan_update_stop0 of 5 parameters describedSet the status (todo, done, skipped) and/or notes of one stop in a plan. Name the stop by label (its label, else its station, body or system) or by index in the plan's stops, from 0; give exactly one. Mark a stop done when the player has finished there; returns the plan with the new next_stop.
plan_delete0 of 1 parameter describedDelete a saved plan.
plan_export0 of 4 parameters describedExport a plan as Markdown (default) or JSON. Without path, returns the text (markdown) or the plan (json). With path (absolute or ~/...), writes the file. A JSON file can be loaded again with plan_import.
plan_import0 of 3 parameters describedLoad a plan from a JSON file written by plan_export (absolute or ~/... path). id replaces the id in the file. Refuses to replace an existing plan unless overwrite is true.
prefs_getno parametersGet the commander's stored travel preferences used by station searches: maximum arrival distance (soft/hard/off), planetary, fleet carrier and megaship rules, minimum pad (auto = current ship), permit-locked systems (allow/exclude), and the travel-time model (jump range and the share of the journal's unladen range that auto uses, seconds per jump, supercruise curve, docking, planetary time, value of time in cr/h).
prefs_set0 of 1 parameter describedChange stored travel preferences with a partial patch, for example {"stations":{"max_arrival_ls":{"value":2000}}}. Saved for future sessions; returns the full preferences. For a one-off change pass `preferences` to the search tool instead.
activity_getno parametersWhat the commander was last doing: a short saved note (kind, summary, optional plan_id), its age, and the commander's current location from the journal. Call it at the start of a conversation. When the location or age says the player has moved on, ask before relying on the note.
activity_set0 of 4 parameters describedReplace the saved note of what the commander is doing, so the next conversation can pick it up. kind and summary (at most 500 characters: where, the goal, and progress) are required; plan_id names the active route or build plan. Update it when the player starts something new or the goal changes. clear: true deletes the note.
settings_openno parametersOpen the ed-mcp settings page in the browser, where the user enters or clears Inara and EDSM API keys and commander names. Keys entered there apply at once, without a restart, and sync (encrypted) when a sync folder and password are set. Never ask the user to type a key into the chat; use this page.
settings_statusno parametersWhere ed-mcp keeps its data: the sync folder and whether it is available, whether secrets are encrypted, where each API key comes from (environment or saved), whether a Frontier login is saved, any sync conflict copies, and notes on settings that look mismatched between Claude apps. An `update` line says when a newer ed-mcp release is available. Never returns key values.
catalog_blueprint0 of 2 parameters describedEngineering blueprint by journal id (e.g. FSD_LongRange) or name (e.g. 'Increased range'): materials per grade 1-5 with material symbol, grade and trade group, and the experimental effects available for the module. Give module when the name is shared by several modules.
catalog_engineers0 of 3 parameters describedWith blueprint (and optional module): engineers who apply it, their max grade, location and invite/unlock requirements, best first. With engineer: that engineer's location, requirements and every blueprint they offer.
catalog_material0 of 1 parameter describedEngineering material by name or symbol: kind, grade, trade group, other materials in the same trade group, and material trader exchange rules.
catalog_module0 of 1 parameter describedOutfitting module by journal symbol (e.g. Int_Hyperdrive_Size5_Class5) or name: class, rating, mount and engineering group. Returns total matches and at most 20 items.
inara_commander_profile0 of 1 parameter describedCommander profile from Inara: ranks with progress, allegiance, power, main ship type, squadron and Inara URL. Omit name for your own commander. Inara does not expose location, loadout or materials; use EDSM or CAPI tools for those. Cached 60 s.
inara_community_goalsno parametersRecent and active community goals from Inara. Cached 60 s.
edsm_commander_locationno parametersCommander's last known system, coordinates, docked station and ship, from EDSM. Cached 60 s.
edsm_commander_materials0 of 1 parameter describedCommander's engineering materials (raw and manufactured), encoded data, and cargo, from EDSM. kinds defaults to all three. Cached 60 s.
spansh_find_stations2 of 9 parameters describedFind the best stations near a system, ranked by travel time and cost, that sell a module or ship, or offer a service: material traders, tech brokers, interstellar factors, black market, Universal Cartographics, Vista Genomics, Search and Rescue, refuel, repair, restock, shipyard, outfitting, market and more (see the service enum). Give exactly one of module, ship, service. Module names are generic (e.g. 'Frame Shift Drive') with class 1-8 and rating A-I; give class and rating to compare prices. Applies the commander's stored travel preferences (arrival distance, station types, pad size from the current ship, travel-time model); override any of them for this call with `preferences` (same shape as prefs_set's patch) or ignore them with use_preferences=false. Returns total (Spansh matches before preferences; 10000 means 10000 or more), matched (matches after preferences among the stations fetched: the nearest 50, or up to 100 when the arrival limit was relaxed). Stations are ranked by estimated travel time (jumps plus supercruise, docking and planetary time) and, for purchases, by effective cost = price + travel time × the commander's credits_per_hour. Each station has jumps, travel_s, travel_min, arrival_assumed, effective_cost and discount_pct (versus the median price); recommended explains the trade-off. Stations in permit-locked systems are left out unless permit_systems is allow, which keeps them with needs_permit: true. Also returns any relaxed rules, the applied preferences and notes. Cached 5 min.
spansh_system0 of 2 parameters describedLook up a system by exact name: coordinates, allegiance, permit, and its stations sorted by distance from arrival (limit applies to stations). Cached 24 h.
spansh_route0 of 5 parameters describedPlot a neutron-boosted route between two systems for a laden jump range in LY. Returns waypoints with jumps needed to reach each. May take a while; if it says still plotting, call again with the same arguments. Cached 5 min.
trade_route4 of 11 parameters describedPlan a multi-hop trade run with the Spansh trade planner and rank it by profit per hour. Starts at from_system/from_station, or the docked station from the game journal. Cargo and capital default to the journal's ship and credits (else 7 t and 1000 cr). Pad size, planetary stations and fleet carriers and a hard arrival-distance limit come from the commander's travel preferences. Returns hops with commodities to buy and sell, profit, travel_min, total_profit, total_travel_min and profit_per_hour (from the travel-time model), plus the resolved inputs. Spansh takes one to several minutes: if the result is status pending, call again with the inputs it shows to resume. Finished routes are cached 5 min.
commodity_prices2 of 9 parameters describedFind the best stations near a system to sell or buy one commodity, from Spansh market data, filtered and ranked with the commander's travel preferences. Stations show price, demand (sell) or supply (buy), market_age_hours and travel_min. Give amount (tonnes) to rank by value = price × amount ∓ travel time × credits_per_hour (minus when selling, plus when buying); otherwise ranked by price. Searches within max_distance_ly of near (default the journal's current system) and only markets updated within max_price_age_days. Stations must have demand or supply of at least amount (else 1). Stations in permit-locked systems are left out unless permit_systems is allow. recommended names the best station and why. Cached 5 min.
trade_loops5 of 14 parameters describedFind repeatable trade loops: two or three stations, where a leg can run empty. start "here" (default) finds loops through your docked station; start "any" finds the best loops anywhere within radius_ly of near (default: where you are). Ranked by sustained profit per hour: thin markets that cannot refill a full hold every lap rank low. Uses Spansh market data (check each price's age). Cargo and capital default to the journal. Loops through permit-locked systems are left out unless permit_systems is allow. Legality is not checked.
systems_by_state3 of 10 parameters describedFind the nearest populated systems with a faction in a given state (e.g. War, Civil War, Election, Boom, Outbreak), or by government, allegiance, controlling power or security. near defaults to the journal location. War and Civil War results say conflict_zones: likely (settlements are not checked). Faction states come from player visits: check age_hours. Uses one Spansh search of all populated systems in radius_ly, cached for an hour; the first call can take 10 s.
massacre_targets2 of 6 parameters describedFind pirate (Anarchy) factions near you with good sources of stackable pirate massacre missions, as Inara's 'nearest massacre missions' does. Sources are populated systems within 10 ly of the target; a primary source has no other pirate faction in other systems within 10 ly (its own pirate faction does not count, as missions send you to another system), so all its massacre missions are for this target. Sources with a faction in War, Civil War or Election are excluded and listed. stack_size is the number of distinct giving factions in the primary sources. Targets whose farthest star is beyond max_star_ls (default 10,000) are left out, because fights there can be far from the arrival star. Ranked by stack_size, then spread_ls, then distance. Results are candidates: mission boards are not published. Pads are listed, not filtered. near defaults to the journal location.
ground_cz_targets1 of 8 parameters describedFind likely ground (on-foot) conflict zones near you: systems with a faction at War or Civil War, settlements owned by the warring factions, and a Frontline Solutions station close to those settlements (within max_gap_ls of distance from the arrival star, so on the same planet or its moons) that meets the minimum pad; left_out.pad_too_small counts systems where only smaller-pad stations are close. Data older than max_age_hours (default 6) is left out: wars often end at the daily tick. The best station is the quickest to dock at (a planetary landing counts against it), then the one with most warring settlements nearby. For the top detail_count results, body detail says whether the station is a planetary port on the settlements' planet (drop: same_body) or an orbital station next to that planet and its moons (drop: orbital). drop: gap_only means the station and settlements are at about the same distance from the arrival star, but the body data could not confirm the same planet or its moons: check each settlement's body. drop: null (with near_body and body_family null, and no body on settlements) means no body detail was fetched: the result is beyond detail_count, the time limit was reached, or the fetch failed. Zones are likely, not confirmed. near defaults to the journal location.
materials_plan2 of 6 parameters describedPlan engineering materials: needs for blueprints (grades, rolls, experimentals) and extra materials, compared with the commander's inventory (journal or EDSM), trades from surplus at exact material trader rates, what is still short, and the best trader of each type near the commander (travel preferences apply).
missions_route3 of 5 parameters describedOrder the stops for accepted missions (from the game journal): passengers, deliveries and hand-ins for completed missions. Uses Spansh coordinates and the travel-time model to minimise time while meeting deadlines; lists late and unroutable missions. The order is exact up to 12 stops and 24 missions with an expiry; above that it is a nearest-first heuristic and deadline handling is best-effort. Planetary stations are inferred from the Spansh station type. `from` and `return_to` must be systems Spansh knows. The first call for systems not seen in the last day can take tens of seconds, because Spansh lookups are rate limited.
route_stops7 of 11 parameters describedOrder the stops of a plan (plan_id) or a list (stops): shops, material traders and engineers for a build, or the systems, bodies and stations of a route. Plan stops marked done or skipped are left out. Uses Spansh coordinates and the travel-time model. For each engineer stop, set `after` to the shops and traders that supply what that engineer needs (the module to buy, the materials to trade). Give `after: []` to an engineer who needs nothing from the other stops, so they can come first. Without your rules, a plan puts every engineer after every shop and trader. Use `one_of` for alternatives, for example two engineers who both do the work; the tool tries every combination (at most 16) and keeps the fastest. `only` and `skip` choose stops from the plan, so one plan can serve several trips. One place (the same engineer, or the same system and station) can be an option in several groups; it is visited once, and each stop's `meets` lists the groups it covers. Leg times are estimates from straight-line jumps; pass plot: true to plot the chosen route with Spansh.
capi_login0 of 1 parameter describedLog in to Frontier's Companion API in the browser. Returns immediately with the login URL; the user finishes in the browser. Call again to check the state; pass force: true to log in again. Logins last 25 days.
capi_profileno parametersLive commander data from Frontier: current system and docked station, current ship with every module and its engineering (blueprint, grade, engineer, experimental), and all owned ships with locations. Does not include materials (use edsm_commander_materials). Cached 60 s.
capi_logoutno parametersForget the stored Frontier login. With a sync password, this logs out every computer that shares the sync folder.
journal_statusno parametersCheck the Elite Dangerous journal folder: whether it exists, the newest journal and how old its last event is, the commander and game version. Use it first when journal data looks wrong or out of date; warnings explain missing folders and stalled Syncthing sync, and also mention a newer ed-mcp release when one is available.
journal_commanderno parametersThe commander's current state from the local game journal: name, credits, location (system, station, docked), ship (type, name, jump range, cargo and fuel capacity) and cargo. as_of is the time of the newest journal event and age_minutes its age; warnings flag stale data (over 30 minutes old) and unreadable journal files.
journal_materials0 of 1 parameter describedEngineering materials the commander holds, from the local game journal, by kind (raw, manufactured, encoded) with counts. Pass kinds to limit the result. as_of is the time of the newest journal event and age_minutes its age; warnings flag stale data (over 30 minutes old) and unreadable journal files.
journal_missionsno parametersAccepted missions (active and complete) from the local game journal: destination, expiry, reward and passenger or cargo details, soonest expiry first. status is active or complete (objectives met, not handed in). origin_system and origin_station are where the mission was accepted (station is null when not docked). expired is true once the expiry has passed. details_missing marks missions accepted before the 14-day journal window (name and expiry only). as_of is the time of the newest journal event and age_minutes its age; warnings flag stale data (over 30 minutes old) and unreadable journal files.
journal_engineersno parametersEngineer progress from the local game journal: invited, unlocked or known, with rank and rank progress. as_of is the time of the newest journal event and age_minutes its age; warnings flag stale data (over 30 minutes old) and unreadable journal files.
journal_exobiology2 of 2 parameters describedExobiology progress in a system from the local game journal (last 14 days). For each body with biological signals: bio_signals (the count from the FSS or surface scan), genera found by the surface scan, each species sampled with samples taken (stage 0/3 to 3/3, analysed once complete; abandoned when another species was started first, which drops an unfinished sample, or after a death), and not_started genera with no sample yet. likely lists, for each genus not started, the species likely on the body (from its scan and Canonn's records of where each species grows) with value and likelihood, most likely first: say they are predictions. unsold_analysed counts species analysed since the last sale of organic data (or death), in any system. The journal has no sample positions. system defaults to the current system; body is a full body name or the part after the system name, such as "A 4". as_of is the time of the newest journal event and age_minutes its age; warnings flag stale data (over 30 minutes old) and unreadable journal files.
journal_exploration1 of 1 parameter describedExploration scans of a system from the local game journal (last 14 days). discovery has the FSS discovery scan body count and progress, and all_bodies_found once the FSS is complete. bodies lists each scanned body, nearest first: type, distance_ls from the arrival star, landable, terraformable, atmosphere, rings, was_discovered and was_mapped (by someone before you), mapped_by_you (surface scan complete), signals, value_scanned (credits from the detailed scan) and value_mapped (credits once mapped efficiently; planets only). The values include the first-discovery and first-mapped bonuses when they apply. system defaults to the current system. as_of is the time of the newest journal event and age_minutes its age; warnings flag stale data (over 30 minutes old) and unreadable journal files.
journal_massacreno parametersProgress of active massacre missions from the local game journal, grouped by target faction and then by giving faction. Each mission has kills_required, kills_counted (from bounties and combat bonds against the target since it was accepted) and kills_left. A kill counts toward the oldest open mission of each giving faction, as the game stacks them; a mission redirected back to its giver is done. A target's kills_left is the most any one giver still needs. The counts are an estimate. uncounted lists massacre missions accepted before the 14-day journal window. as_of is the time of the newest journal event and age_minutes its age; warnings flag stale data (over 30 minutes old) and unreadable journal files.
journal_events3 of 4 parameters describedRaw events from the local game journal (last 14 days), newest first, as the game wrote them. Use it for anything the other journal tools do not cover, instead of reading the journal files. events limits the event names (for example Bounty or Docked); since is an ISO time; system keeps events in that system. limit defaults to 50 (at most 200). Arrays longer than 20 entries are cut, with a last entry that says how many were left out. as_of is the time of the newest journal event and age_minutes its age; warnings flag stale data (over 30 minutes old) and unreadable journal files.
station_info0 of 3 parameters describedWhat the station you last opened a screen at sells, from the game's own files in the journal folder (Market.json, Outfitting.json, Shipyard.json). Complete and current, but only for the latest station of each kind. part: market (commodities sold and bought, each with price, stock or demand and vs_mean_pct), outfitting (modules by group with price), shipyard (ships by price) or all (a short summary of each, the default). commodity filters the market by name; search filters modules by name, group, symbol or class and rating (for example '5A'). Notes flag data that is old or from a station other than the docked one.
build_parse_slef1 of 1 parameter describedParse a SLEF ship build (export from EDSY, Coriolis or Inara) into slots, modules, blueprints, grades and experimental effects. Module names, class and rating are resolved from the game data catalog when available. Accepts SLEF JSON only. An EDSY link (edsy.org/#/L=...) is not SLEF: open it in a browser, click Export..., read the export_slef text input and pass that value, or ask the user to paste the SLEF.
build_stats1 of 2 parameters describedModel a ship build: mass, fuel, jump range, power, speed, shields, armour and weapon damage. The build comes from the latest journal Loadout (the default), the CAPI ship, a SLEF build or a plan's target_build. `changes` apply what-if changes in order: swap, engineer or remove modules. With changes, `diff` lists only the values that changed, and `build` is the changed build as SLEF. Save it with plan_upsert (target_build), in a file or in an artifact. Real builds use their real engineering values; engineering from changes assumes the best roll for the blueprint and grade.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.