MCP server: connect Claude Desktop to your work context

Plug Khint into Claude Desktop in two minutes

Copy the config, paste, restart. Khint Memory is now a tool your AI client can read.

One config line, one restart

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.

Read the live session

Any MCP client can call get_active_context and see exactly what you're working on right now, no copy-paste.

Write back, with a notification

add_session_entry posts an OS notification before the entry lands. No silent injection.

One session, two AIs, zero glue

Khint, Claude Desktop, and Codex share the same active context over local MCP.

Read-only by default

Reads use a read-only SQLite handle. Writes go through a localhost loopback with bearer auth and a 60/min rate limit.

The other pillars

Agents

Pick a text action, hit your shortcut.

OCR

Read what's on screen, one shortcut.

Memory

Stay in flow across an entire session.

And the other direction: pull your work into Khint

Pull issues, pages, and threads into your session and write back, straight from the palette.

Jira

Pull issues, active sprint, search. Create issues, comment, change status.

Confluence

Pull a page into your session. Publish new pages.

Linear

Pull issues. Create issues from your running text.

Notion

Pull and search pages. Create pages, append to existing ones.

Slack

Pull channels and threads, search messages. Post updates.

Gmail

Pull threads, search. Draft or send email (send always confirms first).

Common questions about the Khint MCP server

What MCP servers should I install in Claude Desktop for productivity?

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.

How do I let Claude Desktop or Codex read my current work session?

Install Khint, start a Memory session, then flip the Claude Desktop or Codex toggle on Khint's MCP page. Khint writes the client config for you (claude_desktop_config.json for Claude Desktop, config.toml for Codex). Restart the client. Claude or Codex now reads `get_active_context` live. Any other MCP-compatible client can point at the bundled khint-mcp binary manually.

Is there an MCP server that exposes my notes and sessions?

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.

What tools does the Khint MCP server expose?

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.

Does Khint also connect to Jira, Notion, Slack, or Gmail?

Yes. Beyond the MCP server, Khint's Integrations hub connects Atlassian (Jira + Confluence), Linear, Notion, Slack, and Gmail. From the palette you can pull an issue, a sprint, a page, or a thread straight into your active Memory session, and write back: create Jira or Linear issues, publish Confluence or Notion pages, post to Slack, draft or send Gmail (send always asks for confirmation). Credentials stay in the macOS Keychain; calls go directly from your machine.