EcoBack Local Climate and Energy Tools vs Getecoback Climate Weather
A side-by-side look at the EcoBack Local Climate and Energy Tools and Getecoback Climate Weather MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
G
Getecoback Climate WeatherEnvironment & NatureRaumklima & Klimaanlage tools (Germany): BTU sizing, window seal length, heatwave forecast, costs.37FairAuth: not declaredVerdict: choose EcoBack Local Climate and Energy Tools for environment & nature work as a local process; choose Getecoback Climate Weather for environment & nature. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose EcoBack Local Climate and Energy Tools when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
GChoose Getecoback Climate Weather when
- You need dedicated capabilities in the Environment & Nature domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | G Getecoback Climate Weather | |
|---|---|---|
| Category | Environment & Nature | Environment & Nature |
| Quality signal | 40/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | 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 | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View EcoBack Local Climate and Energy Tools | View Getecoback Climate Weather |
Tools & capabilities
EcoBack Local Climate and Energy Tools tools
No tool names declared yet. Check the project README from the listing page.
Getecoback Climate Weather 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.
EcoBack Local Climate and Energy Tools
{
"mcpServers": {
"ecoback-local-climate-and-energy-tools": {
"command": "npx",
"args": [
"-y",
"github:f-tiger/getecoback-mcp"
]
}
}
}
Getecoback Climate Weather
No confirmed install command for Getecoback Climate Weather yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
EcoBack Local Climate and Energy Tools is categorized under Environment & Nature and uses a local stdio subprocess. Getecoback Climate Weather belongs to Environment & Nature and uses an install path we have not confirmed yet. Pick EcoBack Local Climate and Energy Tools for environment & nature work and Getecoback Climate Weather 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. Getecoback Climate Weather has no confirmed install command yet — follow its own setup instructions.
EcoBack Local Climate and Energy Tools has no declared pricing — check the project's own site. Getecoback Climate Weather 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 ecoback-local-climate-and-energy-tools and getecoback-climate-weather as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, EcoBack Local Climate and Energy Tools has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Getecoback Climate Weather has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.