by nefesh-ai
Real-time human state awareness for AI agents via Model Context Protocol (MCP)
★ 0
GitHub stars
Provides AI agents with real-time awareness of human physiological and emotional state through biometric data analysis, including closed-loop feedback on adaptation effectiveness.
nefesh-mcp-server is a community-built MCP server published by nefesh-ai that provides AI assistants with tools and capabilities via the Model Context Protocol. Real-time human state awareness for AI agents via Model Context Protocol (MCP) It is categorized under ai ml. This server exposes 6 tools that AI clients can invoke during conversations and coding sessions.
You can install nefesh-mcp-server in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
nefesh-mcp-server is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
nefesh-mcp-server is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
We evaluated nefesh-mcp-server against two servers with overlapping tools; this profile had the clearer scope statement.
We wired nefesh-mcp-server into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
I recommend nefesh-mcp-server for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
We evaluated nefesh-mcp-server against two servers with overlapping tools; this profile had the clearer scope statement.
Strong directory entry: nefesh-mcp-server surfaces stars and publisher context so we could sanity-check maintenance before adopting.
nefesh-mcp-server reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Useful MCP listing: nefesh-mcp-server is the kind of server we cite when onboarding engineers to host + tool permissions.
According to our notes, nefesh-mcp-server benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
I recommend nefesh-mcp-server for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
showing 1-10 of 62
A Model Context Protocol and Agent-to-Agent (A2A) server that gives AI agents real-time awareness of human physiological state.
Send sensor data (heart rate, voice, facial expression, text sentiment), get back a unified state with a machine-readable action your agent can follow directly. Zero prompt engineering required.
On the 2nd+ call, the response includes adaptation_effectiveness — telling your agent whether its previous approach actually worked. A closed-loop feedback system for self-improving agents.
Most APIs give you a state. Nefesh tells you whether your reaction to that state actually worked.
On the 2nd+ call within a session, every response includes:
{
"state": "focused",
"stress_score": 45,
"suggested_action": "simplify_and_focus",
"adaptation_effectiveness": {
"previous_action": "de-escalate_and_shorten",
"previous_score": 68,
"current_score": 45,
"stress_delta": -23,
"effective": true
}
}
Your agent can read effective: true and know its previous de-escalation worked. If effective: false, the agent adjusts its strategy. No other human-state system provides this feedback loop.
Add the config without an API key — your agent will get one automatically.
{
"mcpServers": {
"nefesh": {
"url": "https://mcp.nefesh.ai/mcp"
}
}
}
Then ask your agent:
"Connect to Nefesh and get me a free API key for [email protected]"
The agent calls request_api_key → you click one email link → the agent picks up the key. No signup form, no manual copy-paste. After that, add the key to your config for future sessions:
{
"mcpServers": {
"nefesh": {
"url": "https://mcp.nefesh.ai/mcp",
"headers": {
"X-Nefesh-Key": "nfsh_free_..."
}
}
}
}
Sign up at nefesh.ai/signup (1,000 calls/month, no credit card), then add the config with your key:
{
"mcpServers": {
"nefesh": {
"url": "https://mcp.nefesh.ai/mcp",
"headers": {
"X-Nefesh-Key": "YOUR_API_KEY"
}
}
}
}
| Agent | Config file |
|---|---|
| Cursor | ~/.cursor/mcp.json |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
| Claude Desktop | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Claude Code | .mcp.json (project root) |
| VS Code (Copilot) | .vscode/mcp.json or ~/Library/Application Support/Code/User/mcp.json |
| Cline | cline_mcp_settings.json (via UI: "Configure MCP Servers") |
| Continue.dev | .continue/config.yaml |
| Roo Code | .roo/mcp.json |
| Kiro (Amazon) | ~/.kiro/mcp.json |
| OpenClaw | ~/.config/openclaw/mcp.json |
| JetBrains IDEs | Settings > Tools > MCP Server |
| Zed | ~/.config/zed/settings.json (uses context_servers) |
| OpenAI Codex CLI | ~/.codex/config.toml |
| Goose CLI | ~/.config/goose/config.yaml |
| ChatGPT Desktop | Settings > Apps > Add MCP Server (UI) |
| Gemini CLI | Settings (UI) |
| Augment | Settings Panel (UI) |
| Replit | Integrations Page (web UI) |
| LibreChat | librechat.yaml (self-hosted) |
{
"servers": {
"nefesh": {
"type": "http",
"url": "https://mcp.nefesh.ai/mcp",
"headers": {
"X-Nefesh-Key": "<YOUR_API_KEY>"
}
}
}
}
</details>
<details>
<summary><strong>Zed</strong> — uses <code>context_servers</code> in settings.json</summary>
{
"context_servers": {
"nefesh": {
"settings": {
"url": "https://mcp.nefesh.ai/mcp",
"headers": {
"X-Nefesh-Key": "<YOUR_API_KEY>"
}
}
}
}
}
</details>
<details>
<summary><strong>OpenAI Codex CLI</strong> — uses TOML in <code>~/.codex/config.toml</code></summary>
[mcp_servers.nefesh]
url = "https://mcp.nefesh.ai/mcp"
</details>
<details>
<summary><strong>Continue.dev</strong> — uses YAML in <code>.continue/config.yaml</code></summary>
mcpServers:
- name: nefesh
type: streamable-http
url: https://mcp.nefesh.ai/mcp
</details>
All agents connect via Streamable HTTP — no local installation required.
Nefesh is also available as an A2A-compatible agent. While MCP handles tool-calling (your agent calls Nefesh), A2A enables agent-collaboration — other AI agents can communicate with Nefesh as a peer.
Agent Card: /.well-known/agent-card.json
A2A Endpoint: POST https://mcp.nefesh.ai/a2a (JSON-RPC 2.0)
| A2A Skill | Description |
|---|---|
get-human-state | Stress state (0-100), suggested_action, adaptation_effectiveness |
ingest-signals | Send biometric signals, receive unified state |
get-trigger-memory | Psychological trigger profile (active vs resolved) |
get-session-history | Timestamped history with trend |
Same authentication as MCP — X-Nefesh-Key header or Authorization: Bearer token. Free tier works on both protocols.
| Tool | Auth | Description |
|---|---|---|
request_api_key | No | Request a free API key by email. Poll with check_api_key_status until ready. |
check_api_key_status | No | Poll for API key activation. Returns pending or ready with API key. |
get_human_state | Yes | 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 | Yes | 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 | Yes | Get psychological trigger profile — which topics cause stress (active) and which have been resolved over time. |
get_session_history | Yes | Get timestamped state history with trend (rising/falling/stable). |
Your AI agent can get a free API key autonomously. You only click one email link.
request_api_key(email) — no API key needed for this callcheck_api_key_status(request_id) every 10 secondsFree tier: 1,000 calls/month, all signal types, 10 req/min. No credit card.
After adding the config, ask your AI agent:
"What tools do you have from Nefesh?"
It should list the 6 tools above.
| Plan | Price | API Calls |
|---|---|---|
| Free | $0 | 1,000/month, no credit card |
| Solo | $25/month | 50,000/month |
| Enterprise | Custom | Custom SLA |
Prefer the terminal over MCP? Use the Nefesh CLI (10-32x lower token cost than MCP for AI agents):
npm install -g @nefesh/cli
nefesh ingest --session test --heart-rate 72 --tone calm
nefesh state test --json
GitHub: nefesh-ai/nefesh-cli
delete_subjectMIT — see LICENSE.
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.