Clockify MCP Installer

A lightweight desktop installer that connects Clockify to Claude Desktop by configuring the clockify-mcp-server as an MCP server.

It merges a single clockify-time-entries block into your existing claude_desktop_config.json without touching any other MCP servers you already have set up.

What it does

1. Asks for your Clockify API key and validates it via GET https://api.clockify.me/api/v1/user.
2. Clones clockify-mcp-server into ~/clockify-mcp-server (skips if already present).
3. Runs npm install inside the cloned repo.
4. Reads your existing claude_desktop_config.json, merges the Clockify MCP block, writes it back.

Platforms

• macOS (Apple Silicon and Intel)
• Windows 10/11

Prerequisites for end users

The app shells out to git, npm, and tsx, so users need:

• Node.js (includes npm)
• tsx available on PATH
  • macOS Homebrew installs typically end up at /opt/homebrew/bin/tsx.
  • Install globally with npm install -g tsx if missing.
• git

Develop

npm install
npm run tauri dev

Build

npm run tauri build

Artifacts land in src-tauri/target/release/bundle/.

Release

Push a tag like v0.1.0 and the GitHub Actions workflow in .github/workflows/release.yml produces a .dmg (macOS universal binaries) and .msi/.exe (Windows) attached to a draft GitHub Release.

Config paths written

OS	Path
macOS	~/Library/Application Support/Claude/claude_desktop_config.json
Windows	%APPDATA%\Claude\claude_desktop_config.json

MCP block injected

{
  "mcpServers": {
    "clockify-time-entries": {
      "command": "/opt/homebrew/bin/tsx",
      "args": ["/Users/you/clockify-mcp-server/src/index.ts", "--local"],
      "env": {
        "CLOCKIFY_API_URL": "https://api.clockify.me/api/v1",
        "CLOCKIFY_API_TOKEN": "YOUR_KEY"
      }
    }
  }
}

On Windows, command is "tsx" (resolved from PATH).