Gdacs vs Usgs Mrdata
A side-by-side look at the Gdacs and Usgs Mrdata MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Gdacs for environment & nature work as a local process; choose Usgs Mrdata for environment & nature as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Gdacs when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
Choose Usgs Mrdata when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Environment & Nature | Environment & Nature |
| Quality signal | 41/100 · Fair | 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 | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Gdacs | View Usgs Mrdata |
Tools & capabilities
Gdacs tools
No tool names declared yet. Check the project README from the listing page.
Usgs Mrdata 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.
Gdacs
{
"mcpServers": {
"gdacs": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-gdacs"
]
}
}
}
Usgs Mrdata
{
"mcpServers": {
"usgs-mrdata": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-usgs-mrdata"
]
}
}
}
Frequently asked questions
Gdacs is categorized under Environment & Nature and uses a local stdio subprocess. Usgs Mrdata belongs to Environment & Nature and uses a local stdio subprocess. Pick Gdacs for environment & nature work and Usgs Mrdata for environment & nature.
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.
Gdacs has no declared pricing — check the project's own site. Usgs Mrdata 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 gdacs and usgs-mrdata as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gdacs has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Usgs Mrdata has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.