Stormglass Io
stormglass.io provides a global weather API offering high-resolution forecasts and historical data from trusted meteorological institutions.
Verdict
Common use cases
- Route delivery trucks around storm fronts
- Check wave height before offshore crew deployment
- Pull sunrise times for event planning
- Validate elevation data for construction sites
- Compare tide schedules across coastal stations
Integration
- Vendor
- Stormglass Io
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 4
- Composio slug
stormglass_io
Tools
- Get Elevation for Point
Tool to fetch elevation data for a single geographic point. use when you need bathymetry or topography for a specific latitude/longitude.
- Get solar data for a point
Tool to fetch solar irradiation and sun-position data for a specific coordinate. use after confirming lat/lng, desired parameters, and optional iso-formatted start/end.
- Get weather data for a point
Tool to fetch marine and land weather data for a specific coordinate. use after confirming latitude, longitude, and desired parameters.
- List All Tide Stations
Tool to list all available tide stations. use when you need a catalog of stations before querying tide data.
Setup
Setup guide
- 11. Go to stormglass.io and sign up for an account to generate an API key from your dashboard. 2. In Switchy, open Settings > Integrations > MCP Servers and click 'Add Server'. 3. Select 'Stormglass Io' from the list and paste your API key into the authentication field. 4. Click 'Connect' and wait for the green confirmation badge. 5. Open any Space and type '@Stormglass Io get weather data for 40.7128, -74.0060' to test the connection. 6. If the response includes temperature, wind speed, or wave height, the integration is live. 7. Use @Stormglass Io at the start of any message to invoke weather, solar, elevation, or tide station tools inside that Space.
What teammates see: by default, memories from Stormglass Io are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Weather Check for Site
@Stormglass Io get weather data for 34.0522, -118.2437 including temperature, wind speed, and precipitation for the next 6 hoursOpen in a Space →
Solar Irradiation Estimate
@Stormglass Io get solar data for 51.5074, -0.1278 for today, including direct and diffuse irradiationOpen in a Space →
Elevation Profile Lookup
@Stormglass Io get elevation for 37.7749, -122.4194 so we can confirm the site's altitude above sea levelOpen in a Space →
Tide Station Catalog
@Stormglass Io list all tide stations and filter for those within 50 km of Miami, FloridaOpen in a Space →
Marine Forecast for Route
@Stormglass Io get weather data for 25.7617, -80.1918 including wave height, swell period, and wind direction for the next 24 hoursOpen in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@stormglass-io what's the current wave height and wind speed at 37.7749°N, 122.4194°W?
Based on the latest marine weather data for San Francisco Bay, current conditions show significant wave height at 1.2 meters with a period of 8 seconds, wind speed at 12 knots from the northwest, and air temperature at 14°C. Water temperature is 13°C. This data reflects the most recent forecast model run; conditions update hourly.
Demonstrates the MCP's core weather-fetch capability for a single coordinate. Requires an API key with weather-data scope. Note that Stormglass aggregates multiple forecast sources, so response times can vary by region and parameter complexity. Free-tier accounts have daily request limits.
@stormglass-io find all tide stations within 50km of Vancouver and show me today's high tide times
Found 4 tide stations near Vancouver: Point Atkinson (49.33°N, 123.27°W), Vancouver Harbour (49.29°N, 123.11°W), Steveston (49.12°N, 123.18°W), and Tsawwassen (49.00°N, 123.13°W). For today, high tides occur at Point Atkinson at 06:42 (4.8m) and 19:15 (4.6m). This example shows the two-step workflow: first listing stations, then querying tide data for the nearest match.
Showcases the list-stations tool paired with tide queries. The MCP returns station metadata but doesn't auto-filter by radius—the AI handles distance logic. Tide predictions require a separate API call per station, so batching multiple locations can consume quota quickly. Useful for marine planning or coastal logistics.
@stormglass-io get solar irradiance data for 40.7128°N, 74.0060°W over the next 3 days and summarize peak generation windows for a rooftop solar array
Solar data for New York City shows peak direct normal irradiance (DNI) averaging 850 W/m² between 11:00-14:00 local time across the forecast period. Cloud cover reduces output on day 2 (60% coverage), dropping midday DNI to ~400 W/m². Optimal generation windows: Day 1 (11:30-13:45), Day 3 (10:45-14:15). Sunrise/sunset times shift ~2 minutes earlier each day. This synthesis combines hourly irradiance forecasts with sun-position angles to identify high-yield periods.
Illustrates the solar-data tool combined with AI reasoning to extract actionable insights. The MCP returns raw irradiance and sun-angle arrays; the AI interprets trends. Requires start/end timestamps in ISO 8601 format. Historical data access depends on subscription tier—free accounts get 7-day forecasts only.
Use-case deep-dives
When Stormglass wins for solar site surveys at scale
A 6-person solar installation company runs site surveys across three states and needs to pre-qualify roof angles and sun exposure before sending crews. Stormglass is the right call here: the solar data tool pulls irradiation and sun-position for any coordinate, and the elevation tool confirms topography that might shade panels. The team runs batch queries in Switchy during Monday planning, flags high-yield sites, and routes crews accordingly. The API key auth means no OAuth dance, so the ops lead can share one workspace credential. This breaks down if you need real-time weather during install day—Stormglass refreshes hourly, not minute-by-minute. But for pre-survey qualification, it's faster than manual Google Earth tracing and cheaper than sending scouts to every address.
Why this MCP fits small freight brokers with coastal routes
A 3-person freight brokerage coordinates container pickups at four East Coast ports and needs tide windows and weather forecasts to avoid demurrage fees. Stormglass handles this: the tide station list tool catalogs all NOAA points, the weather tool pulls marine forecasts (wave height, wind speed) for each port coordinate, and the team checks conditions in Switchy before confirming pickup times with truckers. Four tools cover the workflow without needing separate NOAA and weather APIs. The constraint is granularity—if your routes hit inland depots more than ports, you're paying for marine data you won't use. But for coastal logistics under 50 shipments a week, this is the simplest stack to avoid weather-related delays and coordinate with port schedules.
When Stormglass is overkill for event planners
A 4-person event production team books outdoor weddings and corporate retreats and wants to assess weather risk 48 hours before setup. Stormglass can do this—the weather tool pulls forecasts for any venue coordinate—but it's borderline. The MCP shines if you're also checking elevation for drainage issues or solar data for tent placement in summer heat. If you only need basic precipitation and temperature, a simpler weather API or even a shared Weather.com bookmark is faster. The API key setup is easy, but you're paying for marine and solar parameters you'll ignore. Use Stormglass if your events span beaches, mountains, or open fields where topography and sun angle matter. For urban venues with standard tents, skip it and save the subscription cost.
Frequently asked
What does the Stormglass MCP do in Switchy?
It pulls weather, marine, solar, tide, and elevation data from Stormglass.io's API into your Switchy workspace. Your AI agents can query current conditions, forecasts, bathymetry, and sun position for any lat/lng coordinate without leaving the conversation. Useful for logistics, marine ops, outdoor planning, or any workflow that needs location-specific environmental data.
Do I need a Stormglass.io API key to use this MCP?
Yes. You authenticate with an API key from your Stormglass.io account. Switchy stores the key securely and passes it with every request. If you're on Stormglass's free tier, watch your daily quota—the MCP doesn't enforce rate limits itself, so heavy agent usage can burn through requests fast.
Can the MCP fetch historical weather or only forecasts?
It can fetch both, depending on the tool and your Stormglass plan. The weather and solar tools accept optional start/end timestamps, so agents can request past data if your API key has historical access. Elevation and tide station lists are static catalogs. Check your Stormglass subscription to confirm which time ranges you can query.
Why use this MCP instead of calling Stormglass's API directly?
The MCP wraps Stormglass's endpoints so your AI agents can request weather data in plain English, without you writing API client code. It handles parameter formatting, error messages, and response parsing. If you're already building custom integrations or need sub-second latency, stick with the raw API. For conversational workflows, the MCP is faster to deploy.
Who on the team should connect the Stormglass MCP?
Whoever owns the Stormglass.io account and can generate an API key. That's usually someone in engineering, ops, or data. Once connected, any Switchy workspace member can ask agents to fetch weather or elevation data—the MCP doesn't expose the key itself, just the query tools.