Nefesh — Real Time Hu… vs Next Devtools MCP | AllMCPs
Side-by-Side Model Context Protocol Comparison
Nefesh — Real Time Human State Awareness vs Next Devtools MCP
In-depth architectural comparison of the Nefesh — Real Time Human State Awareness and Next Devtools MCP 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
Developer Tools · Remote HTTP/SSE
Quality: 48/100 (Fair) | Auth: No auth required
Next Devtools MCP
Developer Tools · Local stdio
Quality: 84/100 (Excellent) | Auth: No auth required
Verdict Summary: Choose Nefesh — Real Time Human State Awareness if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose Next Devtools MCP if your workspace requires Developer Tools 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 when:
You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Real-time human state fusion: stress score from heart, voice, face signals. GDPR compliant.
Official Next.js MCP server for coding agents. Provides runtime diagnostics, route inspection, dev server logs, docs search, and upgrade guides. Requires Next.js 16+ dev server for full runtime features.
Nefesh — Real Time Human State Awareness 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).
Next Devtools MCP Tools (4)
nextjs_index
Discover running Next.js dev servers and list each one's runtime MCP tools.
nextjs_call
Call a runtime tool on a discovered server (errors, routes, logs, Server Actions).
nextjs_docs
Gateway.** Point the agent at version-accurate docs in `node_modules/next/dist/docs/`.
browser_eval
Gateway.** Point the agent at the [`agent-browser`](https://github.com/vercel-labs/agent-browser) CLI for browser automation.
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 Configuration
Nefesh — Real Time Human State Awareness is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, Next Devtools MCP belongs to Developer Tools using local stdio subprocess. Select Nefesh — Real Time Human State Awareness when you need capabilities focused on developer tools and Next Devtools MCP when you require tools for developer tools.