How do I find air quality near my address?

Use the `get_sensors_near_me` tool with your latitude and longitude. Alternatively, search for sensors by bounding box using `get_sensors_by_bounding_box` with corner coordinates. The API will return nearby sensors with current PM2.5, temperature, and humidity readings.

Can I get historical air quality data?

Yes. Use `get_sensor_history` with a sensor index and time range (Unix timestamps). You can specify which fields to retrieve (PM2.5, temperature, humidity) and set an averaging interval (e.g. 3600 for hourly averages). For spreadsheet analysis, use `get_sensor_history_csv` to get data in CSV format.

What does PM2.5 mean and why is it important?

PM2.5 refers to fine particulate matter smaller than 2.5 micrometers — about 30 times smaller than a human hair. These particles can penetrate deep into lungs and enter the bloodstream, causing respiratory and cardiovascular health effects. The WHO guideline is 5 µg/m³ annual average. PurpleAir sensors measure PM2.5 in real-time, making them essential for health advisories and pollution monitoring.

PurpleAir MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: PurpleAir
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to PurpleAir through Vinkius, pass the Edge URL in the `mcps` parameter and every PurpleAir tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="PurpleAir Specialist",
    goal="Help users interact with PurpleAir effectively",
    backstory=(
        "You are an expert at leveraging PurpleAir tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in PurpleAir "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About PurpleAir MCP Server

Access the world's largest hyperlocal air quality dataset through PurpleAir — a global network of over 50,000 low-cost air quality sensors measuring PM2.5, PM10.0, temperature, humidity, pressure, and more. Connect PurpleAir to your AI agent to monitor real-time air quality, track wildfire smoke, analyze pollution trends, and access historical data for any location — all through natural conversation.

When paired with CrewAI, PurpleAir becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call PurpleAir tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Real-Time Air Quality — Get current PM2.5 readings from sensors near any address or coordinate.
Historical Analysis — Retrieve time-series data for trend analysis, pollution events, and compliance reporting.
Geographic Mapping — Find all sensors within a bounding box for city-wide or regional air quality mapping.
Wildfire Smoke Tracking — Monitor PM2.5 spikes during wildfire events across affected areas.
Indoor Air Quality — Access indoor sensor data for workplace health and HVAC optimization.
CSV Export — Download historical data in CSV format for spreadsheet analysis.
Location-Based Queries — Find the closest sensor to any GPS coordinate.
Sensor Filtering — Filter sensors by type (indoor/outdoor), fields, and update recency.

The PurpleAir MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect PurpleAir to CrewAI via MCP

Follow these steps to integrate the PurpleAir MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from PurpleAir

Why Use CrewAI with the PurpleAir MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with PurpleAir through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

PurpleAir + CrewAI Use Cases

Practical scenarios where CrewAI combined with the PurpleAir MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries PurpleAir for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries PurpleAir, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain PurpleAir tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries PurpleAir against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

PurpleAir MCP Tools for CrewAI (10)

These 10 tools become available when you connect PurpleAir to CrewAI via MCP:

get_indoor_sensors

These sensors measure air quality inside buildings, homes, and enclosed spaces. Useful for indoor air quality assessments, HVAC monitoring, and workspace health studies. Get all indoor PurpleAir sensors

get_outdoor_sensors

These are sensors measuring ambient outdoor air quality. Returns current PM2.5, temperature, humidity and other measurements for each sensor. Useful for regional air quality monitoring, wildfire smoke tracking, and urban pollution studies. Get all outdoor (outside) PurpleAir sensors

get_pm25_sensors

5 (fine particulate matter) measurements. PM2.5 is the most important air quality indicator — particles smaller than 2.5 micrometers that can penetrate deep into lungs and bloodstream. Returns current PM2.5 concentrations along with location data. Essential for health advisories, wildfire smoke tracking, and urban pollution monitoring. Get sensors with PM2.5 measurements

get_sensor_data

Returns PM2.5, PM1.0, PM10.0 particle concentrations, temperature, humidity, pressure, VOC levels, and other measurements depending on the sensor model. Use the fields parameter to specify which measurements to return. Essential for monitoring air quality at a specific location. Get real-time data from a specific PurpleAir sensor

get_sensor_history

Returns time-series data for the requested fields (PM2.5, temperature, humidity, etc.) at regular intervals. Use start_timestamp and end_timestamp (Unix timestamps) to define the time range. The average parameter controls data aggregation (e.g. 60 for 1-minute averages, 3600 for hourly). Essential for analyzing air quality trends, identifying pollution events, and compliance reporting. Get historical air quality data from a PurpleAir sensor

get_sensor_history_csv

Same functionality as get_sensor_history but returns data as CSV instead of JSON. Use for offline analysis, charting, or compliance reporting. Requires start_timestamp and end_timestamp parameters. Get historical sensor data in CSV format for analysis

get_sensors_by_bounding_box

Provide the northwest (nwlat, nwlng) and southeast (selat, selng) corner coordinates. Perfect for mapping air quality across a city, neighborhood, or region. Returns all sensors in the area with current readings. Use with fields parameter to customize returned data. Get all sensors within a geographic bounding box

get_sensors_by_index

Provide comma-separated sensor indices in the show_only parameter. Useful when you already know the sensor indices from a previous query and want to get fresh readings without fetching all sensors. Get data for specific sensor(s) by their indices

get_sensors_near_me

Internally uses a bounding box around the point to find nearby sensors. Useful for identifying the closest PurpleAir monitor to any address or coordinate. Returns sensors sorted by proximity with current air quality readings. Find PurpleAir sensors near a specific location

list_sensors

Use the location_type parameter to filter by sensor type (outside=0, inside=1). Use the fields parameter to specify which data fields to return (e.g. name,latitude,longitude,pm2.5_atm,temperature,humidity). By default returns basic sensor info. Use show_only to filter by specific sensor indices (comma-separated). Use modified_since (Unix timestamp) to get only sensors updated after a specific time. Results include sensor metadata and real-time air quality measurements. List PurpleAir air quality sensors with optional filters

Example Prompts for PurpleAir in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with PurpleAir immediately.

"What's the air quality near San Francisco right now?"

"Show me the PM2.5 trend for sensor 12345 over the last 24 hours."

"Find all outdoor sensors in Los Angeles and show me their PM2.5 readings."

Troubleshooting PurpleAir MCP Server with CrewAI

Common issues when connecting PurpleAir to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

PurpleAir + CrewAI FAQ

Common questions about integrating PurpleAir MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.