MCP server for OpenWeatherMap API integration
Connect MCP Openweathermap to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for OpenWeatherMap API integration. The mcp openweathermap mcp server is what makes that connection.
A Model Context Protocol (MCP) server that provides comprehensive weather data and forecasts through the OpenWeatherMap API. This server enables AI assistants to access real-time weather information, forecasts, air quality data, and location services.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
OPENWEATHER_API_KEY — Your OpenWeatherMap API key (required for stdio transport only)PORT — Server port for HTTP transport (default: 3000)MCP_TRANSPORT — Transport type: stdio or httpStream (default: stdio)MCP_ENDPOINT — HTTP endpoint path (default: /stream)Prerequisites — The Prerequisites tool exposed by this serverSetup — 1. Clone the repository: bash git clone https://github.com/robertn702/mcp-openweathermap.git cd mcp-openweathermapBuild — The Build tool exposed by this serverSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Configuration is passed through the environment: OPENWEATHER_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Openweathermap's toolset — OPENWEATHER_API_KEY, PORT, MCP_TRANSPORT and 4 more — is a fair guide to whether it matches your workflow. It is maintained by robertn702; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP Openweathermap's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| OPENWEATHER_API_KEY | Your OpenWeatherMap API key (required for stdio transport only) |
| PORT | Server port for HTTP transport (default: 3000) |
| MCP_TRANSPORT | Transport type: stdio or httpStream (default: stdio) |
| MCP_ENDPOINT | HTTP endpoint path (default: /stream) |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Setup | 1. Clone the repository: bash git clone https://github.com/robertn702/mcp-openweathermap.git cd mcp-openweathermap |
| Build | The Build tool exposed by this server. |
{
"mcpServers": {
"openweathermap": {
"command": "npx",
"args": ["mcp-openweathermap"],
"env": {
"OPENWEATHER_API_KEY": "your-api-key-here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| OPENWEATHER_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.