Emailmd vs Nefesh — Real Time Human State Awareness for AI
In-depth architectural comparison of the Emailmd and Nefesh — Real Time Human State Awareness for AI MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Emailmd
Communication · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Nefesh — Real Time Human State Awareness for AI
Communication · Remote HTTP/SSE
Quality: 47/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Emailmd if you need specialized Communication tools running via a local process. Choose Nefesh — Real Time Human State Awareness for AI if your workspace requires Communication integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Emailmd when:
You need dedicated capabilities in the Communication domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Markdown to responsive, email-safe HTML conversion, Plain text email version generation, Linting for email deliverability issues.
Write and preview emails from your assistant. Renders markdown into email-safe HTML that holds up in Outlook and Gmail, lints drafts for deliverability problems, and returns a live preview link. Hosted with no API key, or run it locally with npx emailmd mcp.
Fuses biometric signals into a stress score (0-100) for AI adaptation. MCP + A2A native.
Emailmd is categorized under Communication and uses a local stdio subprocess. In contrast, Nefesh — Real Time Human State Awareness for AI belongs to Communication using remote streaming HTTP/SSE transport. Select Emailmd when you need capabilities focused on communication and Nefesh — Real Time Human State Awareness for AI when you require tools for communication.
Request a free API key. You MUST ask the user for their real email first. Do not invent or guess emails. The user receives a verification link they must click. Poll with `check_api_key_status` until ready.
check_api_key_status
Poll for API key activation using the same email the user provided. Returns `pending` or `ready` with API key.
get_human_state
Get stress state (0-100), `suggested_action` (maintain/simplify/de-escalate/pause), and `adaptation_effectiveness` — a closed-loop showing whether your previous action reduced stress.
ingest
Send biometric signals (heart rate, HRV, voice tone, expression, sentiment, 30+ fields) and get unified state back. Include `subject_id` for trigger memory.
get_trigger_memory
Get psychological trigger profile — which topics cause stress (active) and which have been resolved over time.
get_session_history
Get timestamped state history with trend (rising/falling/stable).
Nefesh — Real Time Human State Awareness for AI vs Slack Mcp Server