Nasa Firms vs Site Intelligence
A side-by-side look at the Nasa Firms and Site Intelligence MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Nasa Firms for aerospace & astrodynamics work as a local process; choose Site Intelligence 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 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.
Choose Site Intelligence when
- You need dedicated capabilities in the Aerospace & Astrodynamics domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
RAPIDAPI_KEY, BEELOCATE_RAPIDAPI_HOST. - You want tools like
site_score.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aerospace & Astrodynamics | Aerospace & Astrodynamics |
| Quality signal | 41/100 · Fair | 48/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 | PLATFORM_NASA_FIRMS_KEY | RAPIDAPI_KEYBEELOCATE_RAPIDAPI_HOST |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View Nasa Firms | View Site Intelligence |
Tools & capabilities
Nasa Firms tools
No tool names declared yet. Check the project README from the listing page.
Site Intelligence tools 1
site_score
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.
Nasa Firms
{
"mcpServers": {
"nasa-firms": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-nasa-firms"
],
"env": {
"PLATFORM_NASA_FIRMS_KEY": "YOUR_PLATFORM_NASA_FIRMS_KEY_HERE"
}
}
}
}
Site Intelligence
{
"mcpServers": {
"site-intelligence": {
"command": "uvx",
"args": [
"site-intelligence-mcp"
],
"env": {
"RAPIDAPI_KEY": "YOUR_RAPIDAPI_KEY_HERE",
"BEELOCATE_RAPIDAPI_HOST": "YOUR_BEELOCATE_RAPIDAPI_HOST_HERE"
}
}
}
}
Frequently asked questions
Nasa Firms is categorized under Aerospace & Astrodynamics and uses a local stdio subprocess. Site Intelligence belongs to Aerospace & Astrodynamics and uses a local stdio subprocess. Pick Nasa Firms for aerospace & astrodynamics work and Site Intelligence 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.
Nasa Firms has no declared pricing — check the project's own site. Site Intelligence 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 nasa-firms and site-intelligence as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Nasa Firms has a quality signal of 41/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Site Intelligence has 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.