Weather MCP Server by Meteosource

Name: Weather MCP Server by Meteosource
Author: Meteosource

by Meteosourceversion 0.1.2i★ –iRuns in the cloud

Registry namecom.meteosource/weather

Install

Overview

Description from the maker (original English)

Forecasts, severe-weather alerts, air quality, 20-year weather history, solar and wind production.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Other
You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

claude mcp add --transport http weather https://mcp.meteosource.com/mcp --header 'Authorization: Bearer {api_key}'

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "weather": {
      "url": "https://mcp.meteosource.com/mcp",
      "headers": {
        "Authorization": "Bearer {api_key}"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "weather": {
      "type": "http",
      "url": "https://mcp.meteosource.com/mcp",
      "headers": {
        "Authorization": "Bearer {api_key}"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

Authorization secret required HTTP header
Bearer token carrying your Meteosource API key. The plan the key is on decides which tools are available.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain meteosource.com (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 32484 servers in this category
Published to the registry more recently than 75% of the other 32484 servers in this category
Basic checks equal to or better than 100% of the other 32484 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Weather MCP Server by Meteosource safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: Authorization

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.2) reached the registry 11 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Recta

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

Recta

by RectaBuild

Cheaper cross-chain stablecoin routes for AI agents; 5 % of the verified saving, nothing if none.

Computer or cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Weather MCP Server by Meteosource

Weather data for AI agents. Meteosource hosts the server at

https://mcp.meteosource.com/mcp

It speaks the Model Context Protocol over Streamable HTTP. Connect it to Claude Code, Claude Desktop, Codex, Antigravity or any other MCP client, send your Meteosource API key in a header, and the agent can look up forecasts, official weather warnings, air quality, twenty years of historical weather and the production of PV systems and wind farms.

There is nothing to install and nothing to host. The server keeps no key of its own: every request is served on the key it carries, within the plan that key is on.

Tools

Tool	What it does
`search_places`	Turns a place name, a postal code or coordinates into a `place_id` for the other tools
`get_forecast`	Current conditions, hourly (up to 168 h) and daily (up to 30 days) forecast, minute-by-minute precipitation and warnings for up to 20 locations in one call; a `variables` filter keeps the answer small
`get_alerts`	Official severe-weather warnings for up to 20 locations; returns only the locations that have one. USA, EU and Canada
`get_weather_history`	Past weather, hourly (up to 14 days per call), daily or monthly (up to 366 days per call), aggregated on the server. `normals=true` adds long-term normals and records; `wind_distribution` gives hours per wind-speed bin for turbine siting
`get_air_quality`	Hourly air quality about four days ahead: index, PM10, PM2.5, NO₂, SO₂, O₃ and more
`get_solar_production`	Output of a PV system, given its location, module and inverter power, tilt and orientation: power per hour, energy per day or month, from 20 years back to four days ahead
`get_wind_production`	Output of a wind farm, given its location, turbine model, count or capacity, hub height and terrain: power per hour, energy per day or month, from 20 years back to four days ahead

The server tells the agent how the tools fit together, so a question like "will it rain in Brno tomorrow" ends up as a search_places call followed by get_forecast without you spelling that out.

Before you connect

You need a Meteosource API key. Sign up at meteosource.com (the free plan is enough to try the forecast tools) and copy the key from your account.

The key travels with every request in the Authorization header as Bearer . Each setup below comes down to two values: the URL above and that header.

The rest the server works out itself. It asks Meteosource which plan the key is on and serves the tools that plan includes; a tool outside the plan answers with a sentence saying so. See Plans and limits.

Connect

Claude Code

One command:

claude mcp add --transport http meteosource https://mcp.meteosource.com/mcp \

--header "Authorization: Bearer YOUR_METEOSOURCE_API_KEY"

This registers the server for the current project. Add --scope user to have it in every project. claude mcp list shows whether it connected; inside a session, /mcp lists the tools.

To share the setup with a team without sharing the key, commit a .mcp.json at the project root and let everyone keep their key in an environment variable:

"mcpServers": { "meteosource": { "type": "http", "url": "https://mcp.meteosource.com/mcp", "headers": { "Authorization": "Bearer ${METEOSOURCE_API_KEY}" } } } }

Claude Desktop and claude.ai

Connectors belong to your account, so one added on the web is also there in the desktop app and the other way round.

Open Customize > Connectors (in the desktop app: Settings > Connectors) and click Add custom connector.
Name it Meteosource; the URL is https://mcp.meteosource.com/mcp.
Under Authentication choose No sign-in.
Under Request headers add Authorization with the value Bearer YOUR_METEOSOURCE_API_KEY. Type the word Bearer and the space yourself: Claude sends the value exactly as you enter it.
Click Add. In a chat, open the + menu, choose Connectors and switch Meteosource on.

On Team and Enterprise plans an Owner adds the connector under Organization settings > Connectors and members connect to it from Customize > Connectors. The free plan allows one custom connector.

Codex

Codex CLI, the Codex app and the IDE extension read one file, ~/.codex/config.toml, so the server is configured once for all three. From a terminal:

codex mcp add meteosource --url https://mcp.meteosource.com/mcp \

--bearer-token-env-var METEOSOURCE_API_KEY

and export METEOSOURCE_API_KEY in your shell profile. The section this writes to the file:

[mcp_servers.meteosource]

url = "https://mcp.meteosource.com/mcp" bearer_token_env_var = "METEOSOURCE_API_KEY"

The Codex app has its own dialog (Settings > MCP servers > Add server, type Streamable HTTP), but no field for the key. If the app shows the server as failed, it did not get the variable: an app started from the Dock or the Start menu does not see what you export in a terminal. Put the key in the file instead:

[mcp_servers.meteosource]

url = "https://mcp.meteosource.com/mcp" http_headers = { Authorization = "Bearer YOUR_METEOSOURCE_API_KEY" }

Codex gives a tool call 60 seconds by default. The first request for a year of archive at a location sends 365 requests to Meteosource and can take longer than that, so give this server more time:

tool_timeout_sec = 600

Restart Codex after editing the file (in the app, Restart on the MCP servers page). codex mcp list shows the result; /mcp in a session lists the connected servers.

Antigravity

The IDE and the CLI (agy) share one configuration file: ~/.gemini/config/mcp_config.json for all projects, or .agents/mcp_config.json inside a project. Add:

"mcpServers": { "meteosource": { "serverUrl": "https://mcp.meteosource.com/mcp", "headers": { "Authorization": "Bearer YOUR_METEOSOURCE_API_KEY" } } } }

The key is written out literally; Antigravity does not expand environment variables in this file. If you use the project-level file, keep it out of version control.

In the IDE the same file is reachable from the agent panel: the … menu, MCP Servers, Manage MCP Servers, View raw config. In the CLI, /mcp opens the MCP manager, which shows the connection status and reloads the configuration.

Other clients

Any client that supports MCP over Streamable HTTP works with the same two values, the URL and the header. The server also accepts the key as X-API-Key: , for clients that have a field for an API key but not for a whole header.

Try it

What's the weather in Brno this weekend?
Are there any weather warnings for Prague, Vienna and Munich right now?
Compare last January in Berlin with the long-term normal, day by day.
How many hours of wind above 10 m/s did 49.2, 16.6 see in 2025, month by month?
Air quality in Kraków for the next two days, hour by hour.
How much would a 10 kWp south-facing roof at 50.08, 14.43 have produced last week? (Renewables plan)

Plans and limits

One key is on one Meteosource plan, and the plan decides what the server serves. The weather tools are for the Free, Startup and Standard plans; what each plan includes, and how far back its archive reaches, is on the pricing page. The production tools need the Renewables plan, which in turn has no weather tools.

Days older than the plan's archive need Meteosource's historical add-on. Without it the API refuses such a day with "not allowed to access historical data this old"; the tool reports that for the location concerned and the rest of the call succeeds, so start inside the plan's range.

Per call: up to 20 locations; hourly archive and production up to 14 days, daily or monthly up to 366 days; at most 400 location-days (locations × days) in one call, so a long analysis is several calls. Each location, and each archive or production day, is one request against the key's quota, at the rate limit of its plan. The server keeps a cache, so repeating a call soon afterwards usually costs little or nothing. Cached data is cleared after a while, so a repeat after a longer gap counts against the quota again.

What the agent receives

Time series come back as tables, columns once and rows as arrays, with nested fields flattened (wind_speed, probability_storm, cloud_cover_total). That is four to seven times fewer tokens than the raw API: a week of hourly forecast is about 12 kB, a year of daily archive about 16 kB. The variables parameter trims it further when the agent only needs a few fields. Units default to the local convention of each location; units="metric" forces SI.

Your key and your data

Your key is used only to call Meteosource on your behalf. It is never stored in full and never appears in a URL.
Caches are kept per key. Nothing fetched for one key is ever served to another.
The service records that a call happened, which tool it used and how it went, so the service can be operated.
HTTPS only. A request over plain HTTP is refused, so a key cannot be sent in the clear by mistake.

Troubleshooting

The tools appear in the client without a key; only a tool call needs one. When a call fails, the agent gets a sentence it can show you.

The agent reports	What to do
"No Meteosource API key was supplied…"	The header did not arrive. Check its name and that the value starts with `Bearer` (with the space).
"Meteosource does not know this API key…"	The key is mistyped or revoked. Copy it again from your account.
"This Meteosource API key is disabled…" (or blocked, revoked)	Contact Meteosource support.
"This API key is on the 'standard' tier, which has no production endpoints…"	The production tools need the Renewables plan.
"This API key is on the 'renewables' tier, which has only the production endpoints…"	The weather tools need a weather plan.
"Meteosource cannot verify this API key right now…"	Meteosource's key service did not answer. Try again in a few minutes.
"Meteosource request quota exceeded for this API key…"	The plan's request quota is used up for the period.
"not allowed to access historical data this old" for a location	The day is outside the plan's archive. Shorten the range or add the historical add-on.
"This call would need N location-days (limit 400)…"	Split the request into shorter ranges or fewer locations.
The call times out in the client	A first archive call over many location-days takes a while. Raise the client's timeout (Codex: `tool_timeout_sec`) or ask for a shorter range first; the second run is served from cache.

Questions about your key or plan go to Meteosource support. For the server itself, open an issue in this repository.

About this repository

This repository holds the documentation of the hosted server and its entry for the MCP Registry, server.json. The server is listed there as com.meteosource/weather; clients and catalogs that read the registry pick it up from that entry. The server itself runs at Meteosource; there is nothing here to install.

License

MIT, see LICENSE.

Weather MCP Server by Meteosource

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Recta

README from the maker

Weather MCP Server by Meteosource

Tools

Before you connect

Connect

Claude Code

Claude Desktop and claude.ai

Codex

Antigravity

Other clients

Try it

Plans and limits

What the agent receives

Your key and your data

Troubleshooting

About this repository

License