Git vs HelioSPICE
A side-by-side look at the Git and HelioSPICE MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Git for version control work as a local process; choose HelioSPICE for aerospace & astrodynamics as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Git when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
repo_path, context_lines, target.
Choose HelioSPICE when
- You need dedicated capabilities in the Aerospace & Astrodynamics domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
XHELIO_SPICE_KERNEL_DIR. - You want tools like
get_ephemeris, compute_distance, transform_coordinates.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Aerospace & Astrodynamics |
| Quality signal | 81/100 · Excellent | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | XHELIO_SPICE_KERNEL_DIR |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,540 | 0 |
| Directory activity | 51 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 16 | 6 |
| Full listing | View Git | View HelioSPICE |
Tools & capabilities
Git tools 16
repo_pathcontext_linestargetmessageMERGE_HEADHEADfilesmax_countstart_timestampend_timestampbranch_namebase_branch- +4 more on the listing page
HelioSPICE tools 6
get_ephemerisPosition/velocity — single time (inline) or timeseries (CSV)compute_distanceDistance between two bodiestransform_coordinatesCoordinate frame transformlist_spice_missionsSupported missionslist_coordinate_framesAvailable frames with descriptionsmanage_kernelsKernel cache management
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Git
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"installations"
]
}
}
}
HelioSPICE
{
"mcpServers": {
"heliospice": {
"command": "uvx",
"args": [
"xhelio-spice"
],
"env": {
"XHELIO_SPICE_KERNEL_DIR": "YOUR_XHELIO_SPICE_KERNEL_DIR_HERE"
}
}
}
}
Frequently asked questions
Git is categorized under Version Control and uses a local stdio subprocess. HelioSPICE belongs to Aerospace & Astrodynamics and uses a local stdio subprocess. Pick Git for version control work and HelioSPICE for aerospace & astrodynamics.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Git is listed as free. Auth: no auth required. HelioSPICE has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add git and heliospice as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Git has a quality signal of 81/100 (Excellent) with 51 views, 0 installs and 91,540 GitHub stars. HelioSPICE has 47/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.