knomit for Claude Cowork — MCP memory integration

Claude Cowork talks to knomit through the same stdio MCP bridge that every other MCP client uses. There is no Cowork-specific code in knomit — you register knomit-bridge as an MCP server in Cowork’s configuration, exactly as you would for Claude Desktop.

Prerequisites

1. A running knomit server. The simplest path is the desktop app (Knomit.app / knomit-desktop), which boots the server on a local port and writes the server.json lockfile the bridge uses to discover it. A bare knomit serve on localhost:19278 works too.
2. The knomit-bridge binary on disk. The desktop app symlinks it into $KNOMIT_HOME/bin (default ~/.knomit/bin) on launch; otherwise point at the built binary.

Configure Cowork

Add knomit-bridge as an MCP server in the Claude Cowork config file (see Cowork’s own documentation for the exact config-file location and schema). The entry mirrors a Claude Desktop server:

{
  "mcpServers": {
    "knomit": {
      "command": "/Users/<you>/.knomit/bin/knomit-bridge"
    }
  }
}

Optional arguments select a different repo, or bind the server to a lens instead:

{
  "mcpServers": {
    "knomit": {
      "command": "/Users/<you>/.knomit/bin/knomit-bridge",
      "args": ["--repo", "work"]
    }
  }
}

• Exactly one of --repo <name> or --lens <name> is required — there is no default repo to fall back to. --lens connects to /api/v1/lenses/<name>/mcp instead, and the two are mutually exclusive.
• There is no --profile flag. Profile is a per-repo server setting; the ?profile= query parameter is deprecated and ignored.
• If the server is not on the default port and the lockfile isn’t found, pass the base URL as a positional argument (or set KNOMIT_BASE_URL), e.g. "args": ["http://localhost:19278"].

Once registered, Cowork sees the eight knomit MCP tools — see MCP tools. knomit_repos is the one to call first: it takes no parameters and returns the binding name plus a mount table (name, repo id, branch, read or read+write role, and the src:// source slug where one is set), which tells a Cowork session what it is actually pointed at.

Note

Unlike the Claude Code integration, Cowork does not use the knomit-bridge claude init scaffolding — there are no project skills or hooks, it is purely the MCP server wiring. The bridge does not auto-recover a session if the server dies; the client owns restart. It resolves the base URL once at startup — positional argument, then server.json, then the default — so a server that comes back on a different port needs the bridge restarted too.