Copy the config, paste, restart. Khint Memory is now a tool your AI client can read.
The khint-mcp binary ships inside the app. Add it to claude_desktop_config.json, restart Claude Desktop, and your AI client sees the active session.
Any MCP client can call get_active_context and see exactly what you're working on right now — no copy-paste.
add_session_entry posts an OS notification before the entry lands. No silent injection.
Khint, Claude Desktop, and Codex share the same active context over local MCP.
Reads use a read-only SQLite handle. Writes go through a localhost loopback with bearer auth and a 60/min rate limit.
If you work on a Mac and want Claude to know your active task, install the Khint MCP server. It exposes 5 tools (list_sessions, get_session, get_active_context, search_session_entries, add_session_entry) so Claude can read your active session, search past entries, and append its output back into Khint.
Install Khint, start a Memory session, then add the bundled khint-mcp binary to your client's MCP config (claude_desktop_config.json or Cursor equivalent). Restart the client. Claude or Cursor now reads `get_active_context` live.
Yes. Khint ships its own MCP server. Reads (list/get/search/active context) go through a read-only SQLite handle. Writes (add_session_entry) are proxied through a localhost HTTP loopback with bearer-token auth, 60 writes/min rate limit, and audit log.
Five tools: list_sessions (enumerate Memory sessions), get_session (fetch a session by id), get_active_context (read the live compacted summary), search_session_entries (search across entries), add_session_entry (append to the active session). All over JSON-RPC 2.0, stdio + loopback HTTP, 100% local.
