WellPulse MCP: plug your AI into real wellbeing intelligence

One connection gives your AI credible public benchmarks (CDC PLACES) plus institution-specific wellness signals (trends, snapshots, and alert checks) from your WellPulse data — returned in plain JSON.

Why teams add this

Instant narrative: your AI can explain “what changed” without a human analyst.
Benchmarks that sell: CDC county mental distress context for marketing and reports.
Institution signals: daily trends + alert checks to catch issues early.
One integration: add the MCP once; reuse across copilots, agents, dashboards.

Endpoints

HTTP Stream: https://wellpulse.org/mcp
SSE: https://wellpulse.org/sse

Use JSON-RPC. For HTTP streaming, include: Accept: application/json, text/event-stream.

How it works (visual)

AI app / agent
   │  (MCP tools)
   ▼
WellPulse MCP (this server)
   ├─ Public benchmarks (CDC PLACES)
   └─ Institution data (your DB)
   ▼
Plain-English insights + structured JSON

Designed for fast “ask → answer” loops in copilots and automations.

What you can ask

“What’s our wellness trend for the last 90 days?”
“Did we drop week-over-week? Why might that matter?”
“What’s the CDC mental distress benchmark for this ZIP?”
“Write a short exec update with numbers and context.”

Available Tools

get_mental_health_benchmark — CDC PLACES frequent mental distress (FMD) for a zip or county_fips; returns scope, values, optional national_percentile_rank, and marketing_copy.
get_sector_snapshot — Sector-level snapshot over a window; returns institutions_with_responses, total_responses, avg_wellness_score.
get_basic_alert_guidance — Default alert thresholds by org_size and location_type.
get_institution_snapshot — Counts, avg_wellness_score, last_response_at for an institution over a window.
get_institution_trend_daily — Daily series of { day, avg_wellness, responses }.
get_institution_alert_check — Compares last 7d vs prior 7d; returns drop_pct and alert flag.

Initialize session

curl -s https://wellpulse.org/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc":"2.0",
    "id":1,
    "method":"initialize",
    "params":{
      "protocolVersion":"2025-03-26",
      "capabilities":{},
      "clientInfo":{"name":"example","version":"1.0.0"}
    }
  }'

Capture mcp-session-id response header for subsequent calls.

List tools

curl -s https://wellpulse.org/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "mcp-session-id: <SESSION_ID>" \
  -d '{ "jsonrpc":"2.0", "id":2, "method":"tools/list", "params":{} }'

Call a tool (example)

curl -s https://wellpulse.org/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "mcp-session-id: <SESSION_ID>" \
  -d '{
    "jsonrpc":"2.0",
    "id":3,
    "method":"tools/call",
    "params":{
      "name":"get_mental_health_benchmark",
      "arguments":{"zip":"94597"}
    }
  }'

Notes

ZIP is resolved to county FIPS automatically via public services.
If county data is unavailable, responses include a national fallback.
Institution tools require a valid institution_id present in your database.