Nefesh MCP Server

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. The nefesh mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.

Its toolset

Everything the assistant can do here goes through one of these:

• request_api_key — No
• check_api_key_status — No
• get_human_state — Yes
• ingest — Yes
• get_trigger_memory — Yes
• get_session_history — Yes

Configuration

You will need one environment variable: YOUR_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Nefesh's toolset — request_api_key, check_api_key_status, get_human_state and 3 more — is a fair guide to whether it matches your workflow. It is maintained by tomstuhl; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the nefesh mcp server does with a few real requests.