Status

---
name: status
description: Check whether Nowledge Mem is reachable from Proma, including MCP status, CLI fallback, API URL, and configuration issues after install or update.
---

# Status

Check Nowledge Mem connection status and configuration for Proma.

## When to Use

- User asks "Is nmem working?"
- After installing or updating the plugin
- MCP tools return errors
- Suspicion that the nmem server is down or unreachable

## Usage

**Primary (MCP)**:
```
mcp__nowledge-mem__status
```

**Fallback (CLI)**:
```bash
nmem status
```

## What to Check

1. **MCP tools available?** — Look for `mcp__nowledge-mem__*` in available tools
2. **Server reachable?** — `nmem status` should show `status: ok`
3. **API key configured?** — Check `~/.nowledge-mem/config.json` or `NMEM_API_KEY` env var
4. **mcp.json correct?** — Check `~/.proma/agent-workspaces/default/mcp.json`; top-level key must be `"servers"` (not `"mcpServers"`), type must be `"streamableHttp"`, and the `nowledge-mem` entry must include `"enabled": true`
5. **Hooks configured?** — Check `~/.proma/sdk-config/.claude/settings.json` for `SessionStart`, `UserPromptSubmit`, and `Stop` hooks
6. **Hook scripts present?** — Verify `~/.proma/scripts/save-to-nmem.py` and `~/.proma/scripts/read-working-memory.py` exist
7. **Startup context written?** — Check `~/.proma/agent-workspaces/default/CLAUDE.md` for the `nowledge-mem:start` block

## Troubleshooting

| Symptom | Likely Cause |
|---------|-------------|
| No `mcp__nowledge-mem__*` tools | mcp.json not found or wrong key name; restart Proma |
| MCP tools return errors | Server unreachable; check `nmem status` |
| Hook scripts not firing | Python not in PATH; check `~/.proma/logs/nm-hooks.log` |
| Startup context missing | Run `python3 ~/.proma/scripts/read-working-memory.py`; check `CLAUDE.md` and the hook log |
| "nmem CLI not found" | Install via `pip install nmem-cli` or desktop app |

For remote Mem setups, verify `NMEM_API_URL` and `NMEM_API_KEY` are set, or check `~/.nowledge-mem/config.json`.