Nefesh — Real Time Hu… vs Slack MCP Server | AllMCPs
Side-by-Side Model Context Protocol Comparison
Nefesh — Real Time Human State Awareness for AI vs Slack MCP Server
In-depth architectural comparison of the Nefesh — Real Time Human State Awareness for AI and Slack MCP Server 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
Slack MCP Server
Communication · Remote HTTP/SSE
Quality: 57/100 (Good) | Auth: other
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 Slack MCP Server 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 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).
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).
Slack MCP Server Tools (7)
UserID
User ID (e.g., `U1234567890`)
UserName
Slack username
RealName
User's real name
DisplayName
User's display name
Email
User's email address
Title
User's job title
DMChannelID
DM channel ID if available in cache (for quick messaging)
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, Slack MCP Server belongs to Communication using remote streaming HTTP/SSE transport. Select Nefesh — Real Time Human State Awareness for AI when you need capabilities focused on communication and Slack MCP Server when you require tools for communication.