Mast Nasa vs Noaa Coastwatch
A side-by-side look at the Mast Nasa and Noaa Coastwatch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Mast Nasa for aerospace & astrodynamics work as a local process; choose Noaa Coastwatch 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 Mast Nasa when
- You need dedicated capabilities in the Aerospace & Astrodynamics domain.
- You prefer a local stdio subprocess transport.
- You want tools like
cone_search, mission_search, caom.
Choose Noaa Coastwatch when
- You need dedicated capabilities in the Aerospace & Astrodynamics domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aerospace & Astrodynamics | Aerospace & Astrodynamics |
| Quality signal | 59/100 · Good | 39/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 | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Mast Nasa | View Noaa Coastwatch |
Tools & capabilities
Mast Nasa tools 4
cone_searchSearch MAST around (RA, Dec).mission_searchMission-scoped search with arbitrary criteria.caomGeneric CAOM (Common Archive Observation Model) query.lookup_nameResolve target name → coords.
Noaa Coastwatch 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.
Mast Nasa
{
"mcpServers": {
"mast-nasa": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-mast-nasa"
]
}
}
}
Noaa Coastwatch
{
"mcpServers": {
"noaa-coastwatch": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-noaa-coastwatch"
]
}
}
}
Frequently asked questions
Mast Nasa is categorized under Aerospace & Astrodynamics and uses a local stdio subprocess. Noaa Coastwatch belongs to Aerospace & Astrodynamics and uses a local stdio subprocess. Pick Mast Nasa for aerospace & astrodynamics work and Noaa Coastwatch 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.
Mast Nasa has no declared pricing — check the project's own site. Noaa Coastwatch 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 mast-nasa and noaa-coastwatch as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mast Nasa has a quality signal of 59/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Noaa Coastwatch has 39/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.