Geo vs MCP Weather

A side-by-side look at the Geo and MCP Weather MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

G
GeoLocation Services
Geocoding, truck routing, traffic, weather, and place search via MCP — 11 hosted tools.37FairAuth: not declared
MCP Weather logoMCP WeatherLocation Services · Local subprocess (stdio)Accurate weather forecasts via the AccuWeather API (free tier available).61GoodAuth: api key required

Verdict: choose Geo for location services work; choose MCP Weather for location services as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

G
Choose Geo when

  • You need dedicated capabilities in the Location Services domain.
Explore Geo

MCP Weather logoChoose MCP Weather when

  • You need dedicated capabilities in the Location Services domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: ACCUWEATHER_API_KEY.
  • You want tools like weather-get_hourly, weather-get_daily.
Explore MCP Weather

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
G
Geo
MCP Weather logoMCP Weather
CategoryLocation ServicesLocation Services
Quality signal37/100 · Fair61/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredFreemium
Required env varsNone listedACCUWEATHER_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars—34
Directory activity 0 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
ToolsNot listed2

Tools & capabilities

Geo tools

No tool names declared yet. Check the project README from the listing page.

MCP Weather tools 2

  • weather-get_hourlyGet hourly weather forecast for the next 12 hours
  • weather-get_dailyGet daily weather forecast for up to 15 days

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.

Geo

No confirmed install command for Geo yet — follow the setup steps linked from its listing page rather than a guessed package name.

MCP Weather

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "timlukahorstmann-mcp-weather": {
      "command": "npx",
      "args": [
        "-y",
        "@timlukahorstmann/mcp-weather"
      ],
      "env": {
        "ACCUWEATHER_API_KEY": "YOUR_ACCUWEATHER_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

Geo is categorized under Location Services and uses an install path we have not confirmed yet. MCP Weather belongs to Location Services and uses a local stdio subprocess. Pick Geo for location services work and MCP Weather for location services.

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. Geo has no confirmed install command yet — follow its own setup instructions.

Geo has no declared pricing — check the project's own site. MCP Weather is listed as freemium — a free tier with paid plans. Auth: api key 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 geo and timlukahorstmann-mcp-weather as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Geo has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. MCP Weather has 61/100 (Good) with 4 views, 0 installs and 34 GitHub stars.