WeatherLink MCP by usefulapi

io.usefulapiPublished by usefulapi.ioOfficial publisherv1.0.0Updated Nov 8, 2026

List stations and sensors, read current conditions, history and evapotranspiration in WeatherLink.

The publisher's own server: Ably MCP by usefulapi

VerifiedStreamable HTTPWeb executableLocation & LifestyleData & Analytics

Overview

AI-generated overview

Hosted WeatherLink server that lets an assistant list your weather stations and sensors and read current, historic and evapotranspiration data.

What you can do
  • List stations, nodes and sensors with their metadata
  • Check sensor activity to find sensors that stopped reporting
  • Read the latest observation per sensor for a station (temperature, humidity, wind, rain)
  • Fetch historic records for a station within a 24-hour window
  • Get evapotranspiration reports for WeatherLink Live stations
  • Check usage, request a feature, upgrade or cancel a plan
When to use it
Useful when you want an assistant to answer questions about your own WeatherLink weather stations, such as which are online, current conditions at a site, or how much rain fell yesterday, without building your own integration.
Requirements
Remote MCP endpoint connected by URL; sign-in is via OAuth, and on first connect you supply a WeatherLink API Key and API Secret generated on weatherlink.com. No keys go in the client config. A free plan allows 50 tool calls per month; paid plans raise the limit.
Before you install
You hand your WeatherLink API Key and API Secret to a third-party hosted service, which stores them per user. Historic data and recency depend on your WeatherLink subscription level. The server includes paid plans (Pro and Pro+) with Stripe checkout links, and upgrading or cancelling changes billing; the current period is not refunded on cancel.

Installation

In SourceWeft

  1. Open WeatherLink MCP by usefulapi in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.usefulapi%2Fweatherlink/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "weatherlink-by-usefulapi": {
      "type": "http",
      "url": "https://weatherlink.usefulapi.io/mcp"
    }
  }
}

README

WeatherLink MCP by usefulapi

Use your WeatherLink account from Claude, Cursor, or any MCP client. Read your stations, sensors, current conditions, historic records and evapotranspiration data. Hosted, no local install: connect with your own credentials.

Live endpoint: https://weatherlink.usefulapi.io/mcp · Homepage: https://usefulapi.io

Connect

  • Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://weatherlink.usefulapi.io/mcp.
  • Claude Code: claude mcp add --transport http weatherlink https://weatherlink.usefulapi.io/mcp, then run /mcp to log in.
  • VS Code: Add to VS Code.
  • Cursor and other clients: add the URL as a remote MCP server:
json
{  "mcpServers": {    "weatherlink": {      "url": "https://weatherlink.usefulapi.io/mcp"    }  }}

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, and the login page asks for your WeatherLink credentials.

Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/weatherlink/

On first connect you provide a WeatherLink API Key and WeatherLink API Secret, created on weatherlink.com → Account → Generate v2 Key. The server validates them and stores them per user. No keys go in config files.

Tools

ToolTypeWhat it does
weatherlink_list_stationsreadList stations
weatherlink_list_nodesreadList nodes
weatherlink_list_sensorsreadList sensors
weatherlink_get_sensor_activityreadGet sensor activity
weatherlink_get_current_conditionsreadGet current conditions
weatherlink_get_historic_datareadGet historic data
weatherlink_get_et_reportreadGet evapotranspiration report
weatherlink_usage_statusmetaUsage status (free-tier meter)
weatherlink_request_featuremetaRequest a missing feature
weatherlink_upgrademetaUpgrade to Pro or Pro+
weatherlink_cancel_subscriptionmetaCancel the Pro subscription

read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.

Pricing

PlanPriceLimit
Free$050 tool calls / month
Pro (per user)$9/mo or $90/yr (2 months free)10,000 tool calls / month
Pro+ (per user)$39/mo or $390/yr (2 months free)100,000 tool calls / month

Each paid plan covers this 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].

License

MIT — see LICENSE. Documentation only; the server is hosted.

Source: servers/weatherlink/README.md at commit 0be0869

Tools

7

Version history

1
  1. v1.0.0LatestNov 8, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Usefulapi integrations