List stations and sensors, read current conditions, history and evapotranspiration in WeatherLink. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.
Turn on the WeatherLink connector, then ask in plain words. The AI picks the tools.
For farms, property managers and anyone who runs WeatherLink weather stations.
List your stations and sensors, then check the last reporting time of each sensor. Use the result to find the ones that went quiet.
Find the station id, then get the latest observation per sensor, such as temperature, humidity, wind and rain. The record age depends on your WeatherLink access level.
Get the historic records of one station for a window of up to 24 hours. Each record time marks the end of its recording interval. Your WeatherLink subscription must include historic data.
Get the evapotranspiration data of a WeatherLink Live station. Only WeatherLink Live stations report this data.
List the nodes and sensors that your API Key can access, with their metadata. Use the list to see what each station reports.
The login page asks for your WeatherLink API Key and WeatherLink API Secret.
Create both on weatherlink.com → Account → Generate v2 Key. The key is used only to call the WeatherLink API on your behalf; it is never shown to anyone.
Team and Enterprise: an Owner adds the connector for the organization first.
No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"weatherlink": {
"url": "https://weatherlink.usefulapi.io/mcp"
}
}
} Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"weatherlink": {
"type": "http",
"url": "https://weatherlink.usefulapi.io/mcp"
}
}
} Run these commands. The second one opens the login page:
Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your WeatherLink API Key and WeatherLink API Secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | 10,000 tool calls / month |
| Pro+per user | $39/mo · $390/yr | 100,000 tool calls / month |
Each paid plan covers this WeatherLink server only. Ask your AI to run weatherlink_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with weatherlink_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with weatherlink_upgrade before then undoes the cancel. Or write to [email protected].
weatherlink_list_stationsweatherlink_list_nodesweatherlink_list_sensorsweatherlink_get_sensor_activityweatherlink_get_current_conditionsweatherlink_get_historic_dataweatherlink_get_et_reportweatherlink_usage_statusweatherlink_request_featureweatherlink_upgradeweatherlink_cancel_subscriptionFind stations and sensors that stopped reporting. Read the current weather at one station. Review rainfall and temperature for a past day. Plan irrigation with evapotranspiration data. Inventory the nodes and sensors of your account. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by WeatherLink. The server calls the WeatherLink API with your own WeatherLink access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your WeatherLink API Key and WeatherLink API Secret. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your WeatherLink API Key and WeatherLink API Secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the WeatherLink API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in WeatherLink.
All 7 WeatherLink tools are marked read-only.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this WeatherLink server only. Cancel any time: your paid plan then runs to the end of the paid period. Run weatherlink_usage_status to see how many calls you used.
Ask the AI to run weatherlink_upgrade and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run weatherlink_cancel_subscription. Your paid plan continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with weatherlink_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.