Nefesh — Real Time Human State Awareness for AI vs Emailmd
In-depth architectural comparison of the Nefesh — Real Time Human State Awareness for AI and Emailmd 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
Nefesh — Real Time Human State Awareness for AI
Communication · Remote HTTP/SSE
Quality: 47/100 (Fair) | Auth: No auth required
Emailmd
Communication · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Verdict Summary: Choose Nefesh — Real Time Human State Awareness for AI if you need specialized Communication tools running via a hosted cloud SSE transport. Choose Emailmd if your workspace requires Communication integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Nefesh — Real Time Human State Awareness for AI when:
You need dedicated capabilities in the Communication domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
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.
Fuses biometric signals into a stress score (0-100) for AI adaptation. MCP + A2A native.
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.
Nefesh — Real Time Human State Awareness for AI Tools (6)
request_api_key
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).
Emailmd Tools (6)
Markdown to responsive, email-safe HTML conversion
Plain text email version generation
Linting for email deliverability issues
Live preview via React components or web builder
MCP server exposing render, lint, and docs tools
CLI for local rendering and output control
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Nefesh — Real Time Human State Awareness for AI Configuration
Nefesh — Real Time Human State Awareness for AI is categorized under Communication and uses a remote streaming HTTP/SSE transport. In contrast, Emailmd belongs to Communication using local stdio subprocess. Select Nefesh — Real Time Human State Awareness for AI when you need capabilities focused on communication and Emailmd when you require tools for communication.