
astrodynamics-mcp
io.github.astro-toolsPublished by GitHub account astro-toolsv0.4.0Updated Oct 24, 2026
Astrodynamics MCP server: TLE/SGP4, Lambert, access windows, porkchop, B-plane targeting.
Overview
Local MCP server giving an assistant vetted astrodynamics tools: TLE/SGP4 propagation, Lambert solving, access windows, porkchop scans and B-plane targeting.
- What you can do
- Fetch and propagate satellite orbits: look up TLEs by NORAD ID, name or group and propagate them across epochs in several reference frames, with satellite metadata lookup and time-scale and frame conversions. Solve trajectory problems: Lambert solutions with multi-rev enumeration and two-impulse delta-v, porkchop delta-v/C3 grids, and B-plane targeting for hyperbolic flybys. Compute ground-station access intervals with AOS, LOS and peak elevation. Optional extras add NASA GMAT mission runs, sweeps and script validation, SPICE kernel loading and ephemeris queries, and PNG or CZML trajectory plots.
- When to use it
- Useful when an assistant must produce real orbital numbers rather than estimates: mission design trade studies, transfer and flyby analysis, ground-station contact planning, or checking ephemerides against NASA data. It suits engineers and researchers already working with TLEs, Lambert problems or SPICE kernels.
- Requirements
- Runs locally as a stdio process, installed with uv tool install or pipx from the PyPI package astrodynamics-mcp. Python runtime required. Optional extras [gmat], [spice] and [viz] add tools; the GMAT extra also needs a local NASA GMAT install. Network access to CelesTrak, JPL Horizons and IERS. Space-Track and ESA DISCOSweb need credentials supplied as environment variables or in the session-init _meta block.
Installation
In SourceWeft
- Open astrodynamics-mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
astrodynamics-mcp
A Model Context Protocol server that
gives any MCP-capable LLM client (Claude Code, Cursor, ChatGPT desktop,
custom agents) authoritative astrodynamics tools: TLE/SGP4 propagation,
Lambert solving, ground-station access, time-scale and coordinate-frame
conversions, porkchop scans, B-plane targeting, satellite metadata, and
— with optional extras — full NASA GMAT mission execution ([gmat]),
NASA SPICE / NAIF kernel queries ([spice]), and trajectory visualisation
([viz]).
Why
LLMs reason well about astrodynamics concepts but cannot do the
numerical work — they cannot propagate orbits, solve Lambert problems,
or query SPICE ephemerides. astrodynamics-mcp lets you plug
authoritative tools into any MCP-capable client so the LLM calls vetted
upstream libraries instead of fabricating numbers. Every result carries
explicit units; every tool description tunes against an
Inspect AI eval suite
that measures whether the LLM picks the right tool and binds the right
arguments.
Tools
† Credentialed source. Pass credentials as environment variables for
the stdio transport, or in the session-init _meta block for HTTP — see
Credentials.
A tool called without its credential returns a typed
CredentialRequiredError, never a silent failure.
GMAT tools (optional [gmat] extra)
Install the [gmat] extra and have a local NASA GMAT
install, and five more tools register for driving real GMAT missions
(they stay hidden otherwise):
SPICE tools (optional [spice] extra)
Install the [spice] extra and seven more tools register, backed by NASA
NAIF's CSPICE through spiceypy
(they stay hidden otherwise). They furnish kernels into a process-global
pool and query whatever the pool holds:
The kernel model, the NAIF furnish-from-URL allowlist, and the process-global pool's trust boundary are covered on the SPICE integration page.
Visualisation tools (optional [viz] extra)
Install the [viz] extra and four more tools register, backed by
matplotlib (static PNG plots) and the
gmat-czml sibling (CZML export)
— they stay hidden otherwise. Each returns its picture as an attachment
alongside a numeric summary, so a text-only client still gets the answer:
The attachment model — additive PNG ImageContent / CZML EmbeddedResource
beside the structured summary — and which clients render each kind are covered
on the
Visualisation
page.
Full input / output JSON schemas live on the Tool reference page of the docs site.
Quick start
Install:
Claude Code
Add to your Claude Code MCP settings:
Restart Claude Code. In a chat:
You: Compute the Hohmann Δv from a 250 km circular LEO to GEO.
(The model calls
lambert_solvewith the Hohmann geometry and answers ≈ 3.91 km/s, citing the tool output — not the LLM's own weights.)
Cursor
~/.cursor/mcp.json (or workspace-level .cursor/mcp.json):
Restart Cursor. The tools appear under the astrodynamics server group.
See Pick a client in the docs for ChatGPT desktop, a raw Python MCP smoke client, and the Streamable HTTP transport for remote agents.
Supported clients
What this is not
- Not a general-purpose astrodynamics framework. Wraps vetted upstream libraries; does not re-implement propagators, integrators, or coordinate systems.
- Not an agent framework. Exposes MCP tools; LangGraph, AutoGen, CrewAI, and the LLM clients themselves consume them.
- Not an ML / inference server. Tools that need their own ML models (maneuver detection, neural propagators) belong in separate MCP servers — kept modular for dependency isolation.
- Not a SaaS. Runs locally or in your own infrastructure. No hosted multi-tenant deployment.
- Not a web UI. Tool consumption is via MCP clients; no browser frontend, no desktop app, no notebook widget.
For direct (non-MCP) Python use of the same surfaces, reach for the
upstream libraries:
sgp4,
lamberthub,
skyfield,
astropy,
interplanetary-porkchop,
spiceypy.
Built on
The official Anthropic
modelcontextprotocol/python-sdk
(MIT). The bundled FastMCP server class is the server primitive;
stdio + Streamable HTTP transports are first-class.
Docs and links
- Docs site: astro-tools.github.io/astrodynamics-mcp — getting started, per-client setup, tool reference, recipes, visualisation, data sources, eval suite, FAQ.
- Issue tracker: astro-tools/astrodynamics-mcp/issues
- Discussions: orgs/astro-tools/discussions — usage help and open-ended questions.
- Eval suite: eval/README.md — the regression contract on tool-description quality.
Privacy
astrodynamics-mcp runs entirely on your own machine and collects
nothing — no telemetry, no analytics, no accounts. The only data that
leaves your machine is the query parameters a tool sends to the data
source it wraps (CelesTrak / JPL Horizons / IERS with no auth, and —
only if you configure their credentials — Space-Track and ESA DISCOSweb).
Credentials are read from local environment variables or the session
_meta block and are sent only to their own service over HTTPS. See the
Privacy page
for the full breakdown.
License
MIT — see LICENSE.
Source: README.md at commit 5ef20e7
Tools
0Version history
1- v0.4.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts