Ambient Weather
Ambient Weather provides personal weather stations and an API for accessing real-time and historical weather data.
Verdict
Common use cases
- Check site conditions before field work
- Log daily weather for compliance reports
- Compare readings across multiple locations
- Monitor frost risk for agriculture operations
- Track rainfall totals during storm events
Integration
- Vendor
- Ambient Weather
- Category
- other
- Auth
- API_KEY
- Tools
- 1
- Composio slug
ambient_weather
Tools
- Get Devices
Tool to retrieve a list of user's ambient weather devices with their most recent data. use when you need to list your stations and view their latest readings.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations. 2. Search for Ambient Weather and click Connect. 3. Log into your Ambient Weather account at ambientweather.net, go to Account > API Keys, and generate a new application key and API key. 4. Paste both keys into the Switchy connection form and click Authorize. 5. Return to any Space in Switchy and type '@Ambient Weather list my weather stations' to confirm the connection works. 6. The MCP will return a list of your devices with their most recent readings — temperature, humidity, barometric pressure, wind, and rainfall data. 7. If you see your stations and their current conditions, setup is complete and you can start querying weather data in any conversation.
What teammates see: by default, memories from Ambient Weather 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
Morning Weather Check
@Ambient Weather show me the latest readings from all my weather stations, including temperature, humidity, and wind speed.Open in a Space →
Rainfall Summary
@Ambient Weather get rainfall totals from each of my stations and tell me which location received the most rain.Open in a Space →
Site Condition Report
@Ambient Weather pull the current temperature, wind, and humidity from my station at the north facility and summarize whether conditions are safe for outdoor work.Open in a Space →
Temperature Comparison
@Ambient Weather list the current temperature from all my devices and highlight any station that's more than 5 degrees different from the others.Open in a Space →
Full Station Inventory
@Ambient Weather show me every weather station I have registered, along with the last time each one reported data.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@ambient-weather show me the current temperature and humidity readings from all my weather stations
Your account has two active stations. Station 'Backyard' (MAC ending in A3F2) reports 72.4°F with 58% humidity as of 3 minutes ago. Station 'Rooftop' (MAC ending in B891) shows 73.1°F with 54% humidity, last updated 5 minutes ago. Both stations are reporting normal battery levels and strong WiFi signal.
This example demonstrates the core read capability — fetching device metadata and live sensor data. The MCP returns the most recent reading cached by Ambient Weather's API, typically updated every 5-10 minutes depending on your station's reporting interval. Requires a valid API key with read access to your account's devices.
@ambient-weather what's the wind speed at my rooftop station right now, and has it changed in the last hour?
Your Rooftop station currently reports wind speed at 8.2 mph with gusts up to 12.4 mph. The API returns only the most recent snapshot, so I cannot directly compare to an hour ago. However, the timestamp shows this reading is 4 minutes old. For historical trend analysis, you would need to query Ambient Weather's separate historical data endpoint, which this MCP does not currently expose.
This example highlights a limitation — the Get Devices tool returns only the latest reading, not time-series data. Users expecting historical comparisons will need to supplement with manual API calls or wait for expanded MCP tooling. The response is honest about what the integration cannot do, which sets realistic expectations for weather monitoring workflows.
@ambient-weather check all my stations and let me know if any are showing low battery or connectivity issues
I've checked all three stations on your account. Two are operating normally with strong signals and full batteries. However, your 'Garden Shed' station (MAC ending in C4D7) shows a weak WiFi signal (1 bar) and its last update was 47 minutes ago — significantly longer than the typical 5-minute interval. This suggests either a connectivity problem or the station is powered off. Battery level is reported as 'OK' but the stale timestamp indicates an issue worth investigating.
This example shows how the AI can synthesize health indicators from raw device data — interpreting signal strength, battery status, and update timestamps to surface actionable insights. The MCP provides the data points; the AI's reasoning layer adds diagnostic value. Useful for proactive maintenance alerts in a team Space monitoring remote installations.
Use-case deep-dives
When a single-station MCP beats a weather dashboard
A 6-person landscaping crew checks morning conditions before dispatching teams to job sites. The Ambient Weather MCP pulls live readings from their yard station—temperature, humidity, wind speed—directly into a Switchy thread where the dispatcher is already assigning routes. This works because the team owns one station and needs one data point per morning. If you're comparing multiple sites or need historical trends, you'll hit the tool's limit fast: it lists devices but doesn't expose time-series queries or forecast overlays. The buying call is narrow: you have an Ambient Weather station, your workflow is already in Switchy, and you need current readings without opening a second app.
Live station data for go/no-go decisions
A 3-person event production team runs outdoor markets twice a month. They installed an Ambient Weather station at their venue and use the MCP to pull real-time wind and rain data into a Switchy thread 90 minutes before setup. The MCP's single tool—Get Devices—returns the latest sensor snapshot, which is exactly what they need for a binary decision: set up or postpone. The limitation shows up when they want to compare today's reading to last week's event or check the forecast for tomorrow's backup date. The MCP doesn't store history or predict; it's a live feed. If your decision hinges on current conditions at a station you own, this is the fastest path from sensor to Slack-style thread.
When one API call replaces a monitoring app
A 2-person property management team oversees a vacation rental with an Ambient Weather station on the deck. They check conditions once a day in a Switchy thread to log freeze warnings or high winds that might damage outdoor furniture. The MCP's Get Devices tool returns the station's latest readings in one call, which beats logging into Ambient's web dashboard when you're already triaging maintenance tickets in Switchy. The trade-off: if you manage more than three properties or need alerts (not just manual checks), the single-tool MCP becomes a bottleneck. You'll want a full monitoring platform with webhooks. This MCP is for teams who own the station, check it manually, and want the data where they're already working.
Frequently asked
What does the Ambient Weather MCP do in Switchy?
It connects your Ambient Weather personal weather stations to Switchy so your AI agents can read current conditions from your devices. The MCP pulls live data like temperature, humidity, wind speed, and rainfall from any station linked to your Ambient Weather account. Useful for teams building location-specific workflows or automating reports based on hyperlocal weather.
Do I need admin access to connect Ambient Weather?
You need an Ambient Weather account with at least one registered device and access to generate an API key from your account dashboard. No special admin role required — any account holder can create keys. You'll paste the API key and your application key into Switchy during setup. Both keys are available under your Ambient Weather account settings.
Can the MCP control my weather station or change settings?
No. The Ambient Weather MCP is read-only. It retrieves device lists and current readings but cannot adjust station settings, calibrate sensors, or trigger any actions on the hardware. If you need to change configurations, do that directly in the Ambient Weather app or dashboard. This MCP is purely for pulling data into Switchy workflows.
How is this different from just checking the Ambient Weather app?
The app shows you data; the MCP lets your AI agents act on it. Instead of manually checking readings and copying numbers into reports or alerts, your agents can query conditions on demand and feed that data into automated workflows. Think scheduled weather summaries, conditional logic based on rainfall, or logging trends without opening the app.
Who on my team should connect the Ambient Weather MCP?
Whoever owns the Ambient Weather account and has access to the API keys. Since the MCP reads all devices on that account, connect it once and share the workspace with your team. Only one connection needed per account — multiple team members can build agents that reference the same weather data without each needing their own API key.