Meteors vs Nasa Firms
A side-by-side look at the Meteors and Nasa Firms MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Meteors for aerospace & astrodynamics work as a local process; choose Nasa Firms 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 Meteors when
- You need dedicated capabilities in the Aerospace & Astrodynamics domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_fireballs, get_close_approaches, get_neo_feed.
Choose Nasa Firms when
- You need dedicated capabilities in the Aerospace & Astrodynamics domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PLATFORM_NASA_FIRMS_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aerospace & Astrodynamics | Aerospace & Astrodynamics |
| Quality signal | 53/100 · Good | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | PLATFORM_NASA_FIRMS_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Meteors | View Nasa Firms |
Tools & capabilities
Meteors tools 3
get_fireballsTrack recent meteor impacts and atmospheric explosions detected by US government sensors. Returns impact energy, radiated energy, velocity, altitude, and geographic location.get_close_approachesFind near-Earth asteroids making close approaches within 0.05 AU. Returns object name, approach date, miss distance, velocity, and diameter to identify potentially hazardous objects.get_neo_feedGet near-Earth objects passing Earth during a date range (e.g., "2024-01-01" to "2024-12-31"). Returns asteroid names, sizes, velocities, miss distances, and hazard status.
Nasa Firms tools
No tool names declared yet. Check the project README from the listing page.
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.
Meteors
{
"mcpServers": {
"meteors": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-meteors"
]
}
}
}
Nasa Firms
{
"mcpServers": {
"nasa-firms": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-nasa-firms"
],
"env": {
"PLATFORM_NASA_FIRMS_KEY": "YOUR_PLATFORM_NASA_FIRMS_KEY_HERE"
}
}
}
}
Frequently asked questions
Meteors is categorized under Aerospace & Astrodynamics and uses a local stdio subprocess. Nasa Firms belongs to Aerospace & Astrodynamics and uses a local stdio subprocess. Pick Meteors for aerospace & astrodynamics work and Nasa Firms 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.
Meteors has no declared pricing — check the project's own site. Nasa Firms 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 meteors and nasa-firms as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Meteors has a quality signal of 53/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Nasa Firms has 41/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.