Supported clients¶
astrodynamics-mcp is a standards-compliant MCP server — anything that speaks the Model Context Protocol either over stdio or Streamable HTTP can drive it. The matrix below records which clients the maintainers have verified end-to-end.
Matrix¶
| Client | Transport | Verified | Notes |
|---|---|---|---|
| Claude Code | stdio | ✅ Yes | Reference desktop integration. See Pick a client → Claude Code. |
| Cursor | stdio | ✅ Yes | Same config shape as Claude Code. See Pick a client → Cursor. |
| ChatGPT desktop | stdio | ⏳ Expected to work | MCP support landed in late 2026; verified-working matrix entry pending. |
Raw Python (mcp SDK) |
stdio | ✅ Yes | Smoke client example in Pick a client → Raw Python. |
| Remote agents | Streamable HTTP | ⏳ Expected to work | Stdio + HTTP share a single registered tool surface; transport-equivalence is exercised under pytest. Production deployments not yet documented. |
| LangGraph / AutoGen / CrewAI | (any) | ⏳ Expected to work | astrodynamics-mcp exposes tools; these frameworks consume MCP tools. A cookbook page lands in a later release. |
Legend:
- ✅ Verified — the maintainers have run the full base tool surface through this client and confirmed all calls round-trip. Reported in the project's release notes.
- ⏳ Expected to work — the client speaks compliant MCP; the maintainers have not yet exercised it. Reports of working setups welcome via Discussions.
Attachment rendering¶
The visualisation tools (the optional [viz] extra) return
their output as an attachment beside the structured summary — a PNG
ImageContent from the static-plot tools, or a CZML EmbeddedResource from
czml_trajectory. A client renders the two kinds independently, and a client
that renders neither still gets the always-present ASCII summary. What each
verified client does with the attachment:
| Client | PNG image (plot_*) |
CZML resource (czml_trajectory) |
|---|---|---|
| Claude Code | ✅ Renders inline | 💾 Resource available to save / hand off |
| Cursor | ⏳ Image-capable; not verified | 💾 Resource available to save / hand off |
| ChatGPT desktop | ⏳ Image-capable; not verified | 💾 Resource available to save / hand off |
Raw Python (mcp SDK) |
💾 Bytes available on the result | 💾 Resource text available on the result |
- ✅ Renders inline — the client displays the rendered plot in the chat.
- 💾 Available — the client does not render the artefact itself, but the bytes (PNG) or the document text (CZML) are on the tool result for the client to save to a file or hand to a viewer. No mainstream chat client renders a CZML globe inline; the document is meant for a Cesium viewer, which astrodynamics-mcp does not bundle.
Either way the structured summary and the ASCII recap are always present, so no client is left without an answer. See Visualisation → Which clients render what for the design rationale.
Reporting a working setup¶
If you have astrodynamics-mcp working in a client not on this list, open a Discussion in the astro-tools community space with:
- Client name and version.
- Transport used (stdio / HTTP).
- A snippet of your client config or initialisation code.
- Whether the tools appear and round-trip.
Verified entries land in the next release's matrix.
Reporting a broken setup¶
If a tool call fails against an otherwise-compliant client, open an issue
with the client-compatibility issue
template
when available, or a plain bug report otherwise. Include the failing
tool's input arguments and the error envelope the client received — the
typed error code (e.g. upstream.sgp4_failure,
data_source.celestrak_unreachable) is the fastest path to a diagnosis.