Wellpulse MCP Server

WellPulse MCP server exposing CDC mental health benchmarks and institution wellness insights. The wellpulse mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.

What it actually does

Plug your AI into real wellbeing intelligence — one connection, instant insight.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Its toolset

Everything the assistant can do here goes through one of these:

• get_mental_health_benchmark — Fetches CDC PLACES Frequent Mental Distress (FMD) data for a given ZIP code or county FIPS
• get_basic_alert_guidance — Returns default alert thresholds based on organization size and location type — no institution ID needed
• get_institution_snapshot — A point-in-time snapshot of wellness data for your institution over a given window
• get_institution_trend_daily — Fetches a daily time-series of wellness scores and response counts
• get_institution_alert_check — The get_institution_alert_check tool exposed by this server
• get_sector_snapshot — The get_sector_snapshot tool exposed by this server

Configuration

You will need one environment variable: YOUR_SESSION_ID. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• 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.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the wellpulse mcp mcp server does with a few real requests.

When to reach for it

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. Wellpulse MCP's toolset — get_mental_health_benchmark, get_basic_alert_guidance, get_institution_snapshot and 3 more — is a fair guide to whether it matches your workflow. It is maintained by prmail; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.