Vaisala Xweather
Query current conditions, forecasts, severe-weather alerts, air quality, lightning, road weather and tropical cyclones from your AI assistant. Nineteen read-shaped tools, an API key wrapped in OAuth, a 15,000-access monthly free tier — and no spending cap once you pass it.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Vaisala Xweather via MCP
https://mcp.api.xweather.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Vaisala Xweather Tools & Capabilities (19)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- No life-safety disclaimer is published, and its absence is not a clearance. We found no statement in the MCP docs or the alerts endpoint documentation telling users not to treat the API as a sole source for safety decisions. The authoritative source for any warning remains the agency that issued it, which the record names in
dataSource. - No alert latency figure. Xweather documents the update interval as "near real-time" and the time range as "Latest". It publishes no seconds-or-minutes number we could find.
- European alert coverage is same-day only. Xweather states MeteoAlarm issues today and tomorrow separately and the UK Met Office issues today plus four days, but the API currently provides today's alerts.
- Forecast model provenance is undocumented. The attribution page credits "Global models utilized within conditions, forecasts" to Vaisala Xweather without naming any model, while naming outside sources precisely everywhere else.
- No spending cap. Xweather's pricing page states there are none and that you control your usage. An agent choosing among 19 tools has no built-in budget ceiling; the only automatic brake is the plan's minutely and period rate limit, which returns HTTP 429.
- Call fan-out is large and uneven. Xweather's own estimate for one road weather route is approximately 40 calls, one per turn-by-turn direction. Multi-location and multi-period questions generally cost one call each.
- Multipliers are not flat. Lightning bills at 10x, hail at 12x, air quality at 5x, MapsGL sessions at 150x, against a $0.0006 base rate.
- Pay-as-you-go is US and Canada only. Xweather states this on its pricing page; elsewhere is a separate track.
- The free tier is testing-only by the terms. Vaisala's terms of use state the free developer trial is intended solely for testing and is not intended for commercial use, and limit historical data to the current day, forecast layers to the next 24 hours, and premium lightning endpoints to 20 locations for the current hour.
- The API terms and conditions are not publicly readable.
xweather.com/termsredirects into a JavaScript-only Vaisala document viewer, as does the Vaisala Group general conditions of subscription services. We cannot report what either says about redistribution, resale or AI training — check them before building on the data. - Attribution is mandatory. Xweather requires proper attribution for the API, Raster Maps and MapsGL, and several upstream sources add their own licence terms on top.
- Xweather advises against OAuth for Claude. Its Claude guide cites multiple noted issues with Claude's OAuth as of December 2025 and recommends the API key query parameter instead.
- The API key is account-wide. It authenticates an application, not a person. There is no per-user quota or attribution when several people connect the same credential.
- We could not verify tool behaviour on the wire. The endpoint returns 401 to an anonymous handshake, so no
inputSchema,readOnlyHintordestructiveHintvalues were readable. The read-only classification is from names, Xweather's docs and the scope vocabulary. - Prompts are unconfirmed. Anthropic's snapshot lists no prompt names, and the gated endpoint blocked our own check, so we cannot say whether the server serves any.
- The
www-authenticateURL is a dead link. The header points atoauth.api.xweather.com/.well-known/oauth-protected-resource/mcp, which returns 404. The working descriptor lives on the MCP host.
Frequently asked questions
Where do the severe weather alerts from the Xweather MCP server come from?
From national meteorological agencies, not from Vaisala. Xweather documents its alerts endpoint as carrying alerts issued by the National Weather Service, Environment Canada, MeteoAlarm, the UK Met Office, the Japanese Meteorological Agency and the Australian Bureau of Meteorology. Each record carries a dataSource field naming the issuer. Xweather lists the update interval as near real-time and does not publish a latency figure.
Is the Xweather MCP server free to use?
There is a free tier, but it is narrow. Xweather gives the first 15,000 accesses each month free across all services, with no credit card required, and its pay-as-you-go pricing is available in the US and Canada only. Xweather's own terms of use state the free developer trial is intended solely for testing and is not intended for commercial use, with historical data limited to the current day.
Can an AI agent run up a bill on the Xweather MCP server?
Yes, and Xweather says so plainly: its pricing page states there are no spending caps and that you control your usage. One route question is the sharp edge — Xweather's own documentation estimates roughly 40 API calls for a single Minneapolis-to-Fargo road weather route, one per turn-by-turn direction. Lightning carries a 10x access multiplier.
Does the Xweather MCP server have any write tools?
No write tool appears in either source. All 19 tool names in Anthropic's 2026-08-16 directory snapshot begin with xweather_get_, and every tool Xweather documents is a data query. The single OAuth scope the server advertises is read:api_keys, which is itself read-scoped — a rare case where the scope vocabulary corroborates the tool names rather than contradicting them.
How do you limit which Xweather tools an agent can see?
Xweather supports server-side filtering through query parameters on the endpoint URL. It documents four: include_tags and exclude_tags operate on six named tag groups, while include_tools and exclude_tools take exact tool names. Exclusions win over inclusions. Xweather also recommends combining these with a client-side allowed_tools list for the tightest control.
Which forecast models does Vaisala Xweather use?
Xweather does not name them. Its data source attribution page credits Vaisala Xweather with global models used within conditions and forecasts, without identifying which. It names specific outside sources for other datasets — Copernicus for air quality forecasts, Deutscher Wetterdienst for European radar — so the silence around the core forecast blend is a documented gap, not an oversight.
Do you need a paid Claude plan to add the Xweather connector?
Yes. Xweather's own Claude setup guide states users must have a Claude Pro or Claude Max subscription to use custom MCP servers. You also need an active Xweather API subscription and an application registered in the Xweather dashboard, which yields the combined client id and secret pair the connector authenticates with.
Should you use the API key or OAuth to connect Xweather to Claude?
Xweather recommends the API key. Its Claude guide notes multiple issues with Claude's OAuth as of December 2025 and advises against that option until further notice, pointing users to the query parameter form instead. Claude Desktop cannot send custom headers, so the api_key query parameter is the documented path there rather than an Authorization header.
Do you have to credit Vaisala Xweather when you publish its data?
Yes. Xweather's attribution guide states that all products, naming the Xweather API, Raster Maps and MapsGL, require proper attribution using its allowed marks. It supplies link-back snippets reading powered by Vaisala Xweather. Several upstream sources carry their own conditions too — the Australian Bureau of Meteorology and Environment Canada each impose separate licence terms Xweather links out to.
Sources
- Xweather MCP Server documentation — https://www.xweather.com/docs/mcp-server (fetched 2026-08-19; the directory's
documentationURL; docs version 1.2.2). Sub-pages read: quickstart, authentication, filtering & tool scoping, agents/claude, troubleshooting, tools overview, and all seven tool group pages (general, forecast, air-quality, lightning, tropical, maps, roadweather) · retrieved 2026-08-19 - Xweather MCP roadweather tools — https://www.xweather.com/docs/mcp-server/tools/roadweather (fetched 2026-08-19; source of the ~40-call route estimate) · retrieved 2026-08-19
- Xweather MCP filtering & tool scoping — https://www.xweather.com/docs/mcp-server/filtering-tool-scoping (fetched 2026-08-19; the six tags and four query filters) · retrieved 2026-08-19
- Xweather MCP authentication — https://www.xweather.com/docs/mcp-server/authentication (fetched 2026-08-19; combined-key format, three auth methods, error matrix) · retrieved 2026-08-19
- Xweather MCP Claude agent guide — https://www.xweather.com/docs/mcp-server/agents/claude (fetched 2026-08-19; Pro/Max requirement, OAuth advisory dated by Xweather to 2025-12-18) · retrieved 2026-08-19
- Xweather Weather API alerts endpoint — https://www.xweather.com/docs/weather-api/endpoints/alerts (fetched 2026-08-19; issuing agencies, coverage, update interval,
dataSourcevalues) · retrieved 2026-08-19 - Xweather Weather API data source attribution — https://www.xweather.com/docs/weather-api/resources/credits (fetched 2026-08-19; the full upstream ledger, and the unnamed global models) · retrieved 2026-08-19
- Xweather Weather API attribution guide — https://www.xweather.com/docs/weather-api/resources/attribution (fetched 2026-08-19) · retrieved 2026-08-19
- Xweather Weather API rate limiting — https://www.xweather.com/docs/weather-api/getting-started/rate-limiting (fetched 2026-08-19; minutely and period limits, 429, rate-limit headers) · retrieved 2026-08-19
- Xweather Weather API subscription pricing — https://www.xweather.com/pricing/weather-api-subscription (fetched 2026-08-19; $0.0006 base rate, all multipliers, 15,000 free accesses, "No spending caps") · retrieved 2026-08-19
- Vaisala Terms of Use — https://www.xweather.com/terms-of-use (fetched 2026-08-19; developer trial limitations, no-warranties clause; governs Vaisala websites, not the API) · retrieved 2026-08-19
- Xweather legal index — https://www.xweather.com/legal (fetched 2026-08-19). The Vaisala Group general conditions of subscription services and https://www.xweather.com/terms both resolve into
docs.vaisala.com, a JavaScript-only viewer returning a 2.7 KB loading shell — neither was readable · retrieved 2026-08-19 robots.txt— https://www.xweather.com/robots.txt (fetched 2026-08-19; allows all, disallows/api/,/live-preview/,/global-components/; declares a sitemap; noContent-Signalaxes) · retrieved 2026-08-19llms.txt— https://www.xweather.com/llms.txt (fetched 2026-08-19; a full annotated index, used to locate the alerts and attribution pages rather than guessing URLs). Nollms-full.txtand no/docs/llms.txt— both 404 · retrieved 2026-08-19- Sitemap — https://www.xweather.com/sitemap.xml (fetched 2026-08-19; used to confirm the pricing and legal URLs) · retrieved 2026-08-19
- Live RFC 9728 protected-resource descriptor — https://mcp.api.xweather.com/.well-known/oauth-protected-resource and its
/mcppath-append form (both fetched 2026-08-19, byte-identical; the path-insert form 404s, and both forms onoauth.api.xweather.com404) · retrieved 2026-08-19 - Live RFC 8414 authorization-server metadata — https://oauth.api.xweather.com/.well-known/oauth-authorization-server (fetched 2026-08-19). No
openid-configuration— 404 · retrieved 2026-08-19 - Live anonymous probe — 2026-08-19: an
initializerequest to the endpoint returns HTTP 401 withwww-authenticate: Bearer error="invalid_token", resource_metadata="…"· retrieved 2026-08-19 - Anthropic connector directory — https://claude.ai/directory/295db52b-93db-4429-a489-2be633d33249 (snapshot 2026-08-16; 19 tool names, no prompt names, no permissions field) · retrieved 2026-08-16
- Xweather support — mailto:support@xweather.com
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Analytics
- Developer
- Vaisala Xweather
- Tools
- 19
- Domain
- mcp.api.xweather.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.