ChatCut Desktop MCP

chatcut-desktop-mcp is the public npx entry point for AI desktop hosts that only accept npm-distributed stdio MCP servers. It delegates to the signed, user-scoped launcher generated by ChatCut Desktop; the npm package does not contain a second video-editing server or a desktop binary.

MCP configuration

{
  "mcpServers": {
    "chatcut_desktop": {
      "command": "npx",
      "args": ["-y", "[email protected]"]
    }
  }
}

Install and open the stable ChatCut Desktop app once before connecting. The bridge supports macOS and Windows and writes no non-protocol data to stdout.

Official downloads:

• macOS Apple Silicon: https://api.chatcut.io/desktop/download/macos
• macOS Intel: https://api.chatcut.io/desktop/download/macos-x64
• Windows x64: https://api.chatcut.io/desktop/download/windows

Development

npm test
npm pack --dry-run

For a deterministic smoke test, set CHATCUT_DESKTOP_MCP_LAUNCHER to an executable test launcher. Marketplace configurations should omit the override and use the stable path created by ChatCut Desktop.

The test suite includes a real subprocess smoke test on macOS and Windows. It creates a disposable launcher under a directory containing spaces, parentheses, and &, then checks stdio passthrough and the child exit code. The other platform's native test is skipped, not counted as verified. Run npm test on Windows before publishing a Windows-specific fix.

To verify an unpacked npm tarball, set CHATCUT_BRIDGE_TEST_BIN to that package's bin/chatcut-desktop-mcp.js and run node --test test/launcher.integration.test.js from the source checkout. The tests do not modify Desktop, connector settings, or user projects.

Changes

0.1.1

• Quote the Windows .cmd launcher path so user directories such as C:\Users\Kaiwen Li are passed to the shell as a single command path.
• Keep macOS direct spawning and inherited stdio unchanged. No MCP tools, schemas, expert Skills, or Desktop installation behavior are changed.