Connect Open-Meteo to Codex
Current weather and a 16-day forecast for any coordinates, plus a geocoder that turns a place name into them. No key, no sign-up. Add Toolspoke to Codex once and it can use 2 Open-Meteo actions. Your Open-Meteo credential stays in Toolspoke, and you choose which actions Codex may call.
Set it up in Codex
Three steps, the first one once for every toolkit you will ever add.
Add Toolspoke to Codex
~/.codex/config.toml
[mcp_servers.toolspoke] url = "https://toolspoke.com/mcp"Codex signs in to Toolspoke on its own the first time it connects, so there is no key to paste.
Install Open-Meteo and connect it
Add Open-Meteo to a project in your Toolspoke workspace.
Open-Meteo needs no credential. Install it and it works, and there is nothing of yours for Toolspoke to hold.
Choose what Codex may do
All 2 actions only read, and any of them can be switched off for a project.
What you can ask Codex for
A few of the Open-Meteo actions that only read, so they are safe to try first.
- Current weather and forecast for one pair of coordinates, up to 16 days ahead and 92 days back, free, no key
What Codex can do in Open-Meteo
2 actions read.
Reads
Geocode search
Turn a place name into coordinates: search cities, towns and villages by name and get back latitude, longitude, country, admin region, population, elevation and timezone for each match. This is step one when you have "Berlin" and get_forecast needs 52.52/13.41, pick a result (the first is usually right, but check `country` when the name is ambiguous: there are Springfields in thirty places) and pass its latitude and longitude on. Matching is fuzzy for names of three characters or more, so partial names work. Free, no key. Returns `{"results": [...]}`, or an empty object when nothing matched, treat a missing `results` as no match, not an error.
Get forecast
Current weather and forecast for one pair of coordinates, up to 16 days ahead and 92 days back, free, no key. Ask only for what you need: `current` for conditions right now, `daily` for day-by-day summaries, `hourly` for hour-by-hour detail; each is a list of variable names and the response carries one array per name (with a matching `_units` object). `weather_code` values are WMO codes: 0 clear, 1–3 partly cloudy, 45/48 fog, 51–67 drizzle and rain, 71–77 snow, 80–82 showers, 95–99 thunderstorm. Times are ISO 8601 in the requested timezone, the default here is "auto", the timezone at the coordinates, which is almost always what a person means. Units default to °C, km/h and mm; switch with temperature_unit, wind_speed_unit and precipitation_unit. A 16-day hourly request is a large payload, so prefer `daily` for anything beyond a couple of days. Coordinates come from geocode_search when you only have a place name.
Open-Meteo in Codex: questions
Does Codex see my Open-Meteo credential?
No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Codex only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.
Will 2 actions crowd Codex's context?
No. Toolspoke shows Codex five bridge tools, plus a guide where a toolkit has one, and Codex searches for the Open-Meteo action it needs when it needs it. Adding more toolkits does not add more tools to its list.
Does the same work in ChatGPT?
ChatGPT and Codex share one OpenAI account. In ChatGPT, add a custom MCP connector in its settings and paste the same address.
What does it cost?
Tool calls are free on every plan, and a Open-Meteo call does not run in a sandbox, so it bills nothing.
Try Open-Meteo in Codex
Free to start, and tool calls cost nothing on any plan.