smarterweather-mcp

Use the Smarter Weather MCP servers

Smarter Weather ships two hosted MCP servers. Never wire both into a long-lived client config — they serve different phases:

Server	Endpoint	Auth	Purpose
Weather MCP	https://mcp.smarterweather.com	API key Bearer, OAuth 2.1 + PKCE, or keyless x402	Hosted weather tools: forecasts, alerts, outlooks, raw dataset queries, rendered radar/satellite/sounding imagery
Onboarding MCP	https://mcp.developers.smarterweather.com	Anonymous for discovery; OAuth for account tools	One-time onboarding: get_plans, get_documentation, sign_up, then create_api_key, configure_mcp, usage + billing

Tool descriptors for the weather MCP: https://developers.smarterweather.com/.well-known/mcp-tools.json

Recommended onboarding flow (agents)

1. Connect to the onboarding MCP with no credentials.
2. Call get_plans / get_documentation / sign_up.
3. Complete Clerk OAuth when the host prompts (the stdio bridge runs a loopback callback on port 3334 — ensure it is free).
4. Call create_api_key (idempotent) and configure_mcp.
5. Use the returned key against the weather MCP or the REST API, then remove the onboarding server from the client config.

Anonymous connections to the onboarding MCP list only the three discovery tools; the account-scoped tools appear after OAuth. This is by design, not a failure.

stdio bridge install (local clients)

For clients that cannot speak Streamable HTTP (or whose native OAuth flow is unreliable), use the npm stdio bridges. Do not append @preview — latest is the GA bridge.

// ~/.cursor/mcp.json (or the client's equivalent)
{
  "mcpServers": {
    "smarterweather": {
      "command": "npx",
      "args": ["-y", "@smarterweather/mcp-weather"],
      "env": { "SMARTERWEATHER_API_KEY": "<from shell, not pasted here>" }
    }
  }
}

• Set SMARTERWEATHER_API_KEY in the shell profile and let the client inherit it — pasting the key into the JSON file stores it on disk in cleartext.
• For the onboarding bridge, use @smarterweather/mcp-onboarding with no env; set SMARTERWEATHER_ONBOARDING_AUTH=required to force OAuth up front for account-scoped tools.
• The bridges are thin stdio-to-Streamable-HTTP proxies; all tool implementations run on the hosted servers.