Site Intelligence vs Water Levels
A side-by-side look at the Site Intelligence and Water Levels MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Site Intelligence for aerospace & astrodynamics work as a local process; choose Water Levels 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 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.
Choose Water Levels when
- You need dedicated capabilities in the Aerospace & Astrodynamics domain.
- You prefer a local stdio subprocess transport.
- You want tools like
water_level, water_level_search.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aerospace & Astrodynamics | Aerospace & Astrodynamics |
| Quality signal | 48/100 · Fair | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | RAPIDAPI_KEYBEELOCATE_RAPIDAPI_HOST | 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 | 1 | 2 |
| Full listing | View Site Intelligence | View Water Levels |
Tools & capabilities
Site Intelligence tools 1
site_score
Water Levels tools 2
water_levelCurrent and historical level for a named lake, sea or reservoirwater_level_searchWhich water bodies are monitored, by name, country or continent
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.
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"
}
}
}
}
Water Levels
{
"mcpServers": {
"water-levels": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-water-levels"
]
}
}
}
Frequently asked questions
Site Intelligence is categorized under Aerospace & Astrodynamics and uses a local stdio subprocess. Water Levels belongs to Aerospace & Astrodynamics and uses a local stdio subprocess. Pick Site Intelligence for aerospace & astrodynamics work and Water Levels 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.
Site Intelligence has no declared pricing — check the project's own site. Water Levels 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 site-intelligence and water-levels as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Site Intelligence has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Water Levels has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.