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