Ambee
Ambee provides real-time, hyperlocal environmental data through APIs, offering insights into air quality, weather, pollen, and more.
Verdict
Common use cases
- Alert field crews when AQI exceeds safe thresholds
- Enrich CRM records with local air quality scores
- Forecast pollution for event planning decisions
- Geocode customer addresses for delivery routing
- Monitor pollen levels for health app notifications
Integration
- Vendor
- Ambee
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 16
- Composio slug
ambee
Tools
- Geocode by Place
Tool to transform a place name or address into geographic coordinates. use after confirming the location name to get precise latitude and longitude.
- Get Air Quality by City
Tool to retrieve real-time air quality data for a specific city. use after obtaining a valid city name when current aqi and pollutant levels are needed.
- Get Air Quality by City
Tool to retrieve real-time air quality data for a specific city. use when you have a valid city name and need current aqi and pollutant levels.
- Get Air Quality by Country Code
Tool to retrieve real-time air quality data for a specific country using a 3-letter iso code. use after acquiring the country code and when you want a national overview of air quality.
- Get Air Quality by Latitude and Longitude
Tool to retrieve real-time air quality data for a specific latitude and longitude. use when you need hyper-local air quality readings for given coordinates.
- Get Air Quality by Latitude and Longitude
Tool to retrieve real-time air quality data for a specific latitude and longitude. use when you need hyper-local air quality readings for given coordinates.
- Get Air Quality by Postal Code
Tool to retrieve real-time air quality data for a specific postal code and country. use when you need hyper-local air quality insights by postal code.
- Get Air Quality Forecast by Latitude and Longitude
Tool to retrieve air quality forecast for a specific latitude and longitude. use when you need predicted air quality data up to 48 hours in advance based on geographic coordinates.
- Get Elevation by Latitude and Longitude
Tool to retrieve elevation statistics (min, max, mean) for a specific latitude and longitude. use when you need geospatial elevation data for a location within north america.
- Get Elevation by Place
Tool to retrieve elevation or altitude data for a specific location by place name. use when you have a textual place name and need its elevation in meters.
- Get ILI Forecast by Latitude and Longitude
Tool to retrieve 30-day forecast of influenza-like illness (ili) risk using latitude and longitude. use when you need daily ili risk levels for a specific location, optionally including pollen and weather details.
- Get Wildfire Data by Latitude and Longitude
Tool to retrieve real-time wildfire data for a specific latitude and longitude. use when detailed geospatial wildfire monitoring is required.
- Get Wildfire Data by Place
Tool to retrieve real-time wildfire data for a specific place. use after confirming the place name.
- Get Wildfire Risk Forecast by Place
Tool to retrieve wildfire risk forecast for a specific place. use when you need weekly wildfire risk predictions for a location over the next four weeks.
- Get Wildfire Risk Forecast by Place
Tool to retrieve wildfire risk forecast for a specific place. use when you need weekly wildfire risk predictions for a location over the next four weeks.
- Retrieve latest natural disasters by continent
Tool to retrieve latest natural disaster data for a specific continent. use when you need up-to-date disaster information by continent code.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the MCP Integrations tab. 2. Click 'Add Integration' and select Ambee from the developer tools category. 3. Visit the Ambee dashboard at ambeedata.com, sign in or create an account, then copy your API key from the account settings page. 4. Paste the key into Switchy's configuration dialog and click 'Connect'. 5. Switchy will validate the key against Ambee's API; if successful, you'll see a green checkmark. 6. Open any Space, type '@Ambee get air quality for Seattle' and send — if the MCP replies with AQI data, the connection works. 7. Check your Ambee plan's rate limits and endpoint access to avoid quota errors during heavy use.
What teammates see: by default, memories from Ambee 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
City Air Quality Check
@Ambee get the current air quality for Denver, Colorado. Include AQI, PM2.5, and ozone levels.Open in a Space →
Coordinate-Based Forecast
@Ambee forecast air quality for the next 48 hours at latitude 37.7749, longitude -122.4194.Open in a Space →
Postal Code Lookup
@Ambee get air quality data for postal code 10001 in the United States.Open in a Space →
Geocode Address
@Ambee geocode the address '1600 Amphitheatre Parkway, Mountain View, CA' and return the coordinates.Open in a Space →
Country-Wide Overview
@Ambee get air quality data for country code USA and summarize the national AQI.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Ambee what's the current air quality in Portland, Oregon and should I reschedule my outdoor team event tomorrow?
Based on Ambee's real-time data for Portland, OR (45.5152°N, 122.6784°W), the current AQI is 87 (Moderate) with PM2.5 at 28 µg/m³ and PM10 at 42 µg/m³. The 24-hour forecast shows AQI rising to 105 (Unhealthy for Sensitive Groups) tomorrow afternoon due to wildfire smoke drift. For a team event, sensitive individuals (asthma, heart conditions) may experience discomfort. Consider moving indoors or rescheduling if your group includes vulnerable members.
This example shows Ambee's geocoding + current air quality + forecasting chain. The MCP requires an API key with forecast access enabled. Air quality thresholds vary by region; Ambee uses US EPA standards. Forecast accuracy degrades beyond 24 hours.
@Ambee compare air quality across our office locations in Mumbai, São Paulo, and Berlin right now
Here's the current air quality snapshot across your three offices: Mumbai shows AQI 178 (Unhealthy) with PM2.5 at 92 µg/m³ — recommend limiting outdoor breaks. São Paulo reports AQI 64 (Moderate) with PM10 at 38 µg/m³ — acceptable for normal activity. Berlin has AQI 31 (Good) with low particulate levels — outdoor conditions are favorable. Mumbai's reading reflects typical monsoon-season pollution; consider air purifiers for that location.
Demonstrates batch querying across multiple cities using Ambee's city-based lookup. Each city query counts against your API rate limit (typically 100 requests/minute on standard plans). Results reflect the nearest monitoring station to each city center, not building-specific readings.
@Ambee pull air quality data for postal code 10001 and draft a health advisory for our NYC warehouse staff
Air quality for postal code 10001 (Midtown Manhattan) currently shows AQI 112 (Unhealthy for Sensitive Groups) with elevated ozone at 78 ppb and PM2.5 at 41 µg/m³. Draft advisory: 'Current air quality in our Midtown facility is at unhealthy levels for sensitive groups. Staff with respiratory conditions should minimize strenuous outdoor tasks today. We've increased HVAC filtration and recommend using break rooms rather than outdoor areas. Conditions expected to improve after 6 PM as temperatures drop.' This advisory assumes your facility lacks independent air monitoring.
Shows postal code precision + AI synthesis into actionable team communication. Postal code lookups require both the code and 2-letter country code (US, IN, etc.). Ambee's data comes from government monitoring networks with 1-3 hour lag; it's not real-time sensor data. Always verify against local alerts for emergency conditions.
Use-case deep-dives
When Ambee helps route outdoor work crews safely
A 12-person HVAC company schedules rooftop installations across three metro areas. Their dispatcher uses Ambee's postal-code air quality tool each morning to flag sites where AQI exceeds 150, then reschedules those jobs or assigns respirators. The MCP's geocoding tool converts customer addresses to coordinates, and the 48-hour forecast helps plan multi-day projects around predicted spikes. This works because the team already tracks job sites in a spreadsheet—Switchy pulls that list, queries Ambee in batch, and surfaces the high-risk locations in a shared thread. If your crew is under 5 people or you only work indoors, skip this. But if you're routing 20+ outdoor jobs weekly and air quality matters for safety or equipment performance, Ambee's hyperlocal data beats checking weather apps manually.
When real-time pollution data answers user questions
A 6-person support team at a last-mile delivery app fields questions about delayed shipments in high-pollution zones. Customers ask why their driver rerouted or why delivery windows shifted. The team uses Ambee's city-level air quality tool to pull current AQI and pollutant breakdowns, then pastes that context into ticket responses. Switchy's shared workspace means any agent can query Ambee without leaving the support thread—no API key juggling, no switching to a separate dashboard. The 16-tool count sounds heavy, but support only uses three: city lookup, geocode, and country-code fallback for international queries. If your app doesn't surface environmental factors to users, this is overkill. But if air quality or pollen levels explain service variability, Ambee turns vague apologies into data-backed explanations.
When Ambee narrows ad spend to high-AQI markets
A 4-person growth team at an air purifier brand runs Facebook campaigns in 50 US cities. Every Monday, they pull Ambee's air quality data by city to identify the 10 markets with AQI above 100, then shift ad budget there for the week. The MCP's forecast tool helps them pre-schedule campaigns 48 hours ahead of predicted spikes, catching wildfire smoke or pollen surges before competitors react. Switchy's shared thread logs each week's city rankings, so the team can compare performance across pollution levels without exporting CSVs. This breaks down if you're targeting fewer than 20 cities—manual checks are faster. But if you're running geo-targeted ads at scale and environmental triggers drive purchase intent, Ambee's batch queries save 3 hours of manual research weekly.
Frequently asked
What does the Ambee MCP do in Switchy?
The Ambee MCP pulls real-time and forecasted environmental data—air quality, pollen, weather, and fire alerts—into your Switchy workspace. Your AI agents can query AQI levels by city, postal code, or coordinates, geocode addresses, and retrieve 48-hour air quality forecasts. It's built for teams building location-aware apps, health tools, or environmental dashboards without writing API wrappers.
Do I need an Ambee account to use this MCP?
Yes. You need an active Ambee account and an API key from their developer portal. Switchy stores the key securely and passes it with every request. If your Ambee plan has rate limits or restricted endpoints, those constraints apply to the MCP—Switchy doesn't bypass vendor quotas. Free-tier keys work, but you'll hit daily request caps quickly.
Can the Ambee MCP write data or trigger alerts?
No. The MCP is read-only. It retrieves air quality, pollen counts, weather, and fire data from Ambee's APIs but cannot push data back, create alerts, or modify your Ambee account settings. If you need to act on the data—send a Slack message when AQI spikes, for example—chain the Ambee MCP with another integration like Slack or a webhook tool.
How is this different from calling Ambee's API directly?
The MCP wraps Ambee's REST endpoints so your AI agents can request environmental data in natural language without you writing fetch logic or parsing JSON responses. You skip the boilerplate. The trade-off: you're limited to the 16 tools Switchy exposes. If you need a niche Ambee endpoint not in the MCP, use their API directly or request the tool be added.
Who on my team should connect the Ambee MCP?
Whoever holds your Ambee API key—typically a developer or product lead. Once connected in Switchy, any team member with workspace access can invoke the MCP through AI agents. The key is shared at the workspace level, so treat it like a service account credential. If your Ambee plan bills by request, monitor usage to avoid surprise overages.