Skip to content
knomit

Claude Cowork 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

Section titled “Prerequisites”
  1. A running knomit server. The simplest path is the desktop app (Knomit.app / knomit-desktop), which boots the server on a looknomitck 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 macOS app symlinks it into ~/bin on launch; otherwise point at the built binary.

Configure Cowork

Section titled “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>/bin/knomit-bridge"
    }
  }
}

Optional arguments select a different repo or profile:

{
  "mcpServers": {
    "knomit": {
      "command": "/Users/<you>/bin/knomit-bridge",
      "args": ["--repo", "trunk", "--profile", "chat"]
    }
  }
}
  • --repo defaults to trunk; --profile defaults to code. For a conversational Cowork surface, chat is usually the better profile.
  • 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 seven knomit MCP tools — see MCP tools.