Connect an MCP client

Termyte includes a local MCP server, but the public CLI does not currently include an installer or mcp command. Configure a client to run the built server entry from the installed package. On macOS and Linux, use the built server file directly:

{
  "mcpServers": {
    "termyte": {
      "command": "node",
      "args": ["/absolute/path/to/termyte/dist/server/mcp/server.js"]
    }
  }
}

On Windows, use a small Node launcher because the current server file does not start when called directly by a Windows path:

{
  "mcpServers": {
    "termyte": {
      "command": "node",
      "args": [
        "-e",
        "import(require('node:url').pathToFileURL(process.argv[1]).href).then(m => m.runMcpServer())",
        "C:\\absolute\\path\\to\\termyte\\dist\\server\\mcp\\server.js"
      ]
    }
  }
}

The server uses stdio. It does not listen on a network port. The npm package does not expose a termyte-mcp command. Point the client at the built server file inside the installed package. On Windows, find the global package directory with:

npm root -g

On macOS or Linux, use the same command:

npm root -g

Append termyte/dist/server/mcp/server.js to the returned directory. On Windows, use that full path as the last argument in the Windows example above. MCP can search and inspect stored records, build context, record memory feedback, report health, and work with tasks and handoffs. It does not capture the MCP client’s activity automatically. See the MCP reference for the current tool names and fields.

Daily Work

Integrations

MCP clients

Connect an MCP client

​Connect an MCP client

Connect an MCP client