Wellness MCP Server

If you already use Wellness, the wellness mcp server is the piece that lets your assistant work with it directly. Local-first air-quality MCP for AI agents — AirGradient, AirThings, PurpleAir, IQAir, Awair.

What the server does

Wellness Air is a local MCP server that exposes air-quality readings to any MCP-aware AI agent. It ships with first-class AirGradient support (open hardware + free public API — no auth needed for the 2,000+ public sensors in the worldwide feed). AirThings and PurpleAir are implemented (bring your own free API credentials); IQAir AirVisual and Awair are on the roadmap.

• Public sensors require zero auth. — AirGradient runs an open public API; just pass a locationId
• Owned-sensor tokens stay on your machine. — Set AIRGRADIENT_API_TOKEN only if you own a sensor
• No telemetry. — wellness-air never phones home. The only outbound calls go to the providers you configure
• Read-only. — No tool mutates anything upstream. (air_profile_update writes only to your local shared wellness profile, never to a provider, and requires explicit user intent.)

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• air_agent_manifest — Runtime contract: tool list, supported clients, env vars, recommended first calls
• air_capabilities — Supported providers, configured providers, available metrics, privacy modes
• air_connection_status — Health check + warnings the agent should surface
• air_privacy_audit — What is logged locally vs sent to providers
• air_data_inventory — Metric catalog + AQI band thresholds
• air_list_devices — List devices on an authenticated provider account (AirThings)
• air_daily_summary — Synthesized daily snapshot
• air_compare_locations — Compare AQI across 2-10 locations
• air_search_public_sensors — Discovery helper for AirGradient public map
• air_quickstart — Personalized 3-step setup walkthrough based on current env state
• air_profile_get — Read the shared Delx Wellness profile (location, sensitivities, units)
• air_profile_update — Persist a non-secret patch to the shared wellness profile (explicit intent required)

Credentials and setup notes

Configuration is passed through the environment: WELLNESS_AIR_DEFAULT_PROVIDER, WELLNESS_AIR_DEFAULT_LOCATION, AIRGRADIENT_API_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

The server ships on npm as delx-wellness-hermes, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Wellness's toolset — air_agent_manifest, air_capabilities, air_connection_status and 11 more — is a fair guide to whether it matches your workflow. It is maintained by davidmosiah; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Wellness's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Wellness.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.