nefesh-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| X-Nefesh-Key | No | Your Nefesh API key. Get free at nefesh.ai/signup (1,000 calls/month) or connect without a key and use request_api_key tool. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_human_stateA | Get current unified human state for a session. Call this before generating important responses. |
| ingestA | Send biometric signals from any sensor, get unified state back. |
| get_trigger_memoryA | Retrieve psychological trigger profile for a subject. |
| get_session_historyA | Get state history for a session over time. |
| request_api_keyA | Request a free Nefesh API key. No existing key needed. |
| check_api_key_statusA | Check the status of a pending API key request. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clear distinct role: ingest submits data, get_human_state reads current state, get_trigger_memory and get_session_history cover long-term and recent context, and the two API key tools handle onboarding. Even where get_human_state and ingest both return state-like data, their write/read purposes are explicitly separated by the descriptions.
Most tools follow a verb_noun snake_case pattern (get_human_state, get_trigger_memory, get_session_history, request_api_key, check_api_key_status). The one outlier is 'ingest', which is a bare verb rather than verb_noun, but it is still lowercase and style-consistent. This is a minor deviation rather than a mixed-convention problem.
Six tools is a well-scoped count for a specialized server. Two focus on API key access and four cover the core state/ingest/history/memory workflows, with no redundant helpers or unnecessary bulk. The count feels right for both the domain and the agents that would consume it.
The core workflow is covered: send signals, check current human state, pull session history, and retrieve trigger memory. The primary gaps are not fatal—there is no way to enumerate known sessions/subjects or revoke an API key—but those are auxiliary management features rather than dead ends in the primary state-tracking workflow.