StressZero MCP Burnout Risk Scoring
Let your coding agent score burnout risk on physical, emotional, and effectiveness dimensions so you can slow down before a solo ship week derails you.
Overview
StressZero MCP is a MCP server for the operate phase that scores burnout risk across physical, emotional, and effectiveness dimensions for agent-assisted solo builders.
What is this MCP server?
- Stdio MCP server (npm package stresszero-mcp v1.0.1) for Claude Code, Cursor, and other MCP hosts
- Burnout risk scoring across exactly 3 dimensions: physical, emotional, and effectiveness
- Agent-callable checks so check-ins happen inside the session instead of a separate wellness app
- GitHub-hosted io.github.gomessoaresemmanuel-cpu/stresszero-mcp with MCP 2025-12-11 server schema
- Lightweight npm registry install—no cloud dashboard required in the published metadata
- Server version 1.0.1
- 3 burnout dimensions: physical, emotional, effectiveness
- Transport: stdio via npm registry package stresszero-mcp
What problem does it solve?
Solo builders grind through agent-assisted sprints without a structured read on whether physical drain, emotional load, or slipping effectiveness is pushing them toward burnout.
Who is it for?
Indie hackers and solo devs who want periodic, agent-in-the-loop burnout checks during intense build, ship, or launch stretches—not a full wellness platform.
Skip if: Teams needing HR-grade wellness programs, clinical diagnosis, or passive wearable integrations when the published server only documents dimensional risk scoring via MCP.
What do I get? / Deliverables
After you register the npm stdio server, your agent can return three-dimension burnout risk scores you use to adjust pace, scope, and recovery before quality or health collapses.
- Burnout risk scores across physical, emotional, and effectiveness dimensions
- Agent-accessible wellness signals inside your coding session
- Repeatable operate-phase personal monitoring without leaving the MCP workflow
Recommended MCP Servers
Journey fit
Sustainable solo shipping is an operate-phase problem: you are the production system, and burnout is an operational failure mode that shows up after long build and ship stretches. Burnout risk scoring is personal health monitoring parallel to uptime checks—three dimension scores you revisit while running intense agent-assisted workflows.
How it compares
Personal burnout monitoring MCP, not a project task skill or infrastructure uptime integration.
Common Questions / FAQ
Who is StressZero MCP for?
Solo and indie builders using Claude Code, Cursor, or other MCP clients who want coding agents to surface physical, emotional, and effectiveness burnout risk during heavy shipping periods.
When should I use StressZero MCP?
Use it during long agent sessions, pre-launch crunches, or operate-phase check-ins when you want structured three-dimension risk scores before you commit to more scope or another deploy.
How do I add StressZero MCP to my agent?
Install the npm package stresszero-mcp (v1.0.1), add a stdio MCP server entry pointing at that package in your client config, restart the host, and call the server's burnout scoring tools from chat.