Weather MCP Server Config Generator

Feature Comparison

Config Generator Inputs

Pick a client, package command, and weather API provider, then keep the API key in environment variables. Last updated July 1, 2026; package names and config locations may change.

• Client: Claude Desktop, Claude Code, Cursor, or another MCP-compatible tool.
• Provider: public demo endpoint, OpenWeather-style API, WeatherAPI-style API, or internal forecast API.
• Credential: API key or bearer token stored outside committed config.
• Scope: read-only current weather, forecast, alerts, or geocoding.

Claude Desktop Config Example

Use a local server command and environment variables. Replace package names and keys with the server you actually reviewed.

{
  "mcpServers": {
    "weather": {
      "command": "npx",
      "args": ["-y", "weather-mcp-server"],
      "env": { "WEATHER_API_KEY": "${WEATHER_API_KEY}" }
    }
  }
}

Claude Code And Cursor Examples

For GUI-launched apps such as Cursor, absolute paths can avoid PATH issues. For Claude Code, document the expected command in repo instructions.

Claude Code:
{
  "mcpServers": { "weather": { "command": "node", "args": ["dist/weather-server.js"] } }
}

Cursor:
{
  "mcpServers": { "weather": { "command": "/absolute/path/to/node", "args": ["/repo/dist/weather-server.js"] } }
}

API Key Notes

Weather APIs can have rate limits, paid tiers, and location data considerations. A free weather MCP server is only safe after you understand what provider it calls and where the key is stored.

• Use read-only keys with the smallest useful quota.
• Do not commit keys to mcp.json, Cursor config, or examples.
• Avoid sending precise private locations unless the user explicitly approves that workflow.
• Document quota errors and fallback behavior.

Common Errors

Most weather MCP failures are command, package, credential, or network issues rather than model issues.

• spawn npx ENOENT: Cursor cannot find npx; use an absolute path.
• 401 or invalid key: the weather API key is missing, expired, or in the wrong env var.
• 429 or quota exceeded: reduce agent calls or use a provider limit.
• No tools listed: the server started but did not register MCP tools correctly.
• Wrong location: require city, latitude/longitude, or units explicitly in tool schema.

FAQ