forecast
Pack: tomorrow-io · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/forecast for the schema, then POST the same URL with its arguments for the data.
Get a daily or hourly weather forecast for a location. Returns a list of forecast periods with conditions, temperatures, precipitation probability, and wind. Location can be “lat,lon” coordinates or a city name. Example: forecast({ location: “london”, timestep: “1d”, units: “metric” })
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
location | string | yes | Location to look up — either “lat,lon” coordinates (e.g. “40.71,-74.01”) or a city name (e.g. “new york”) |
timestep | string | no | Forecast granularity: “1d” daily (default) or “1h” hourly |
units | string | no | Unit system: “metric” (default) or “imperial” |
_apiKey | string | no | Tomorrow.io API key (optional — get a free one at tomorrow.io; if omitted the platform key is used) |
Example call
Arguments
{
"location": "london",
"timestep": "1d",
"units": "metric"
}
curl
curl -X POST https://gateway.pipeworx.io/tomorrow-io/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"forecast","arguments":{"location":"london","timestep":"1d","units":"metric"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('forecast', {
"location": "london",
"timestep": "1d",
"units": "metric"
});
More examples
{
"location": "40.71,-74.01",
"timestep": "1h",
"units": "imperial",
"_apiKey": "your-tomorrow-io-api-key"
}
Connect
Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:
{
"mcpServers": {
"pipeworx": {
"url": "https://pipeworx.io/mcp"
}
}
}
Connect to just the tomorrow-io pack
{
"mcpServers": {
"tomorrow-io": {
"url": "https://gateway.pipeworx.io/tomorrow-io/mcp"
}
}
}
See Getting Started for client-specific install steps.