Nasa Eonet vs Next Devtools MCP
A side-by-side look at the Nasa Eonet and Next Devtools MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Nasa Eonet for environment & nature work as a local process; choose Next Devtools MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Nasa Eonet when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
- You want tools like
events, get_event, geojson.
Choose Next Devtools MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
nextjs_index, nextjs_call, nextjs_docs.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Environment & Nature | Developer Tools |
| Quality signal | 59/100 · Good | 86/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 832 |
| Directory activity | 1 views 0 installs 0 upvotes | 9 views 0 installs 1 upvotes |
| Tools | 6 | 4 |
| Full listing | View Nasa Eonet | View Next Devtools MCP |
Tools & capabilities
Nasa Eonet tools 6
eventsNatural hazard events tracked by NASA EONET (the Earth Observatory Natural Event Tracker): wildfires, severe storms, volcanoes, floods, icebergs, landslides, dust and haze. Filter by open or closed status, lookback days, category id, bounding box, reporting source, and magnitude range. Returns each event id, title, category, date-stamped geometry (point or polygon), and links to the reporting agency, answering where wildfires, storms, or eruptions are active now and where they occurred recently.get_eventFetch a single event by EONET id.geojsonSame as events but returns GeoJSON FeatureCollection (good for direct map rendering).list_categoriesReturn all EONET event category definitions (id, title, description, layers) used to filter the events and geojson tools.list_sourcesReturn all official data sources (id, title, homepage URL) that EONET aggregates natural-event records from.list_layersVisualization layer reference (mapping the events to imagery layers).
Next Devtools MCP tools 4
nextjs_indexDiscover running Next.js dev servers and list each one's runtime MCP tools.nextjs_callCall a runtime tool on a discovered server (errors, routes, logs, Server Actions).nextjs_docsGateway.** Point the agent at version-accurate docs in `node_modules/next/dist/docs/`.browser_evalGateway.** Point the agent at the [`agent-browser`](https://github.com/vercel-labs/agent-browser) CLI for browser automation.
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 Eonet
{
"mcpServers": {
"nasa-eonet": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-nasa-eonet"
]
}
}
}
Next Devtools MCP
{
"mcpServers": {
"vercel-next-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}
Frequently asked questions
Nasa Eonet is categorized under Environment & Nature and uses a local stdio subprocess. Next Devtools MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Nasa Eonet for environment & nature work and Next Devtools MCP for developer tools.
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 Eonet has no declared pricing — check the project's own site. Next Devtools MCP is listed as free. Auth: no auth required. 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-eonet and vercel-next-devtools-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Nasa Eonet has a quality signal of 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Next Devtools MCP has 86/100 (Excellent) with 9 views, 0 installs and 832 GitHub stars.