Epwforge MCP vs Git
A side-by-side look at the Epwforge MCP and Git MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Epwforge MCP for environment & nature work as a local process; choose Git for version control as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Epwforge MCP when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
EPWFORGE_API_KEY, EPWFORGE_BASE_URL. - You want tools like
find_station, analyze_weather, chart_weather.
Choose Git when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
repo_path, context_lines, target.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Environment & Nature | Version Control |
| Quality signal | 33/100 · Emerging | 81/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 | EPWFORGE_API_KEYEPWFORGE_BASE_URL | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 91,550 |
| Directory activity | 0 views 0 installs 0 upvotes | 53 views 0 installs 0 upvotes |
| Tools | 4 | 16 |
| Full listing | View Epwforge MCP | View Git |
Tools & capabilities
Epwforge MCP tools 4
find_stationSearch the ~17,000-station GuzzStations catalog by name, country, or coordinates. Optional `compact=True` returns just the newest TMYx per station (6–10× smaller responses for chained agent workflows).analyze_weatherStatistical summary of an EPW. Three modes: `url=` (single file), `urls=[]` (2–10 file comparison), `config={...}` (synthesize a morphed scenario from lat/lon — no EPW content returned). Optional `include_full_ashrae`, `include_improbability`, `include_idf`.chart_weatherInline SVG chart. Single-EPW types: `diurnal`, `temp_carpet`, `wind_rose`, `monthly_boxplot`, `utci_carpet`, `economizer_carpet`, `pv_tilt_azimuth`, `solar_under_events`. Multi-EPW type: `comparison`.generate_weather_fileGenerate and return a downloadable weather file with the full morph stack. Format = `epw` / `ddy` / `csv` / `zip` / `pvsyst`. Supports `ensemble=true` (all SSPs at once).
Git tools 16
repo_pathcontext_linestargetmessageMERGE_HEADHEADfilesmax_countstart_timestampend_timestampbranch_namebase_branch- +4 more on 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.
Epwforge MCP
{
"mcpServers": {
"epwforge-mcp": {
"command": "uvx",
"args": [
"epwforge-mcp"
],
"env": {
"EPWFORGE_API_KEY": "YOUR_EPWFORGE_API_KEY_HERE",
"EPWFORGE_BASE_URL": "YOUR_EPWFORGE_BASE_URL_HERE"
}
}
}
}
Git
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"mcp-server-git"
]
}
}
}
Frequently asked questions
Epwforge MCP is categorized under Environment & Nature and uses a local stdio subprocess. Git belongs to Version Control and uses a local stdio subprocess. Pick Epwforge MCP for environment & nature work and Git for version control.
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.
Epwforge MCP has no declared pricing — check the project's own site. Git 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 epwforge-mcp and git as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Epwforge MCP has a quality signal of 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. Git has 81/100 (Excellent) with 53 views, 0 installs and 91,550 GitHub stars.