Claude Code Haha (cc-haha)

Community

Local-first desktop workspace for Claude Code and AI coding agents — an MCP client with a built-in visual manager, not an MCP server itself.

GitHub source repository ↗

★ 13.9k Stars Category · Dev Tools Very popular

50FMRS · D

Reliability

4/20

Security and permissions

8/20

Maintenance

15/20

Documentation

14/20

Setup experience

9/20

cc-haha is a mature open-source Claude Code desktop workspace covering multi-session management, Git Worktrees, diff review, multi-model support, Computer Use, and IM integration. Based on the available README and materials, however, it is not itself an MCP server that other MCP clients can connect to — it's an MCP client application with a built-in visual manager for connecting to third-party MCP servers.

Read the FMRS scoring method →

Claude Code Haha (cc-haha) is a local-first, cross-platform desktop app for macOS, Windows, and Linux built around Claude Code and other coding agents. It provides multi-session workspaces, Git branch/Worktree launch, file-by-file diff review, a built-in browser preview, GUI permission approval, support for multiple models (Claude, ChatGPT, Grok, DeepSeek, Kimi, Zhipu GLM, and local endpoints), image generation, task-aware desktop pets, and remote access via WeChat, Feishu, DingTalk, Telegram, WhatsApp, and H5. Although the repository is tagged 'mcp', the README describes the app's MCP-related capability as a 'visual MCP manager' for adding and editing third-party MCP servers (STDIO / Streamable HTTP / SSE, with project, shared, or global scope) — there is no evidence in the source material that cc-haha itself exposes any MCP tools or acts as a server that other MCP clients can connect to. In other words, cc-haha functions as an MCP client/management surface, not an MCP server.

Tools

The tool list has not been reviewed yet.

Setup

Download the macOS/Windows/Linux desktop installer from GitHub Releases and install it; on first launch, configure your model provider, API key, and default model in Settings. Public macOS releases are signed and notarized, but draft or unsigned temporary builds may still require one-time manual approval; unsigned Windows installers may trigger SmartScreen — click 'More info' then 'Run anyway'. To run the underlying CLI/server from source for debugging: bun install; cp .env.example .env; ./bin/claude-haha. Because this project is not itself a connectable MCP server, there is no standard MCP client configuration (e.g., an entry in claude_desktop_config.json) for it.

Fit and risk

Best for

Developers already using Claude Code or similar coding agents who want a graphical desktop workspace
Users who need to manage multiple model providers (Claude/ChatGPT/Grok/local models) and multiple MCP server connections in one place
Teams or individuals who want to monitor and approve agent actions remotely through chat apps

Not for

Anyone looking for an MCP server that Claude Desktop, Claude Code, or another MCP client can connect to and call specific tools on
Headless server deployments where a desktop Electron GUI isn't wanted or usable
Users unwilling to install a local Electron desktop app or wary of installing skills from a third-party marketplace

Required permissions

Local file system access for Git Worktree operations, diff review, and project files
Network access to reach model provider APIs and IM channels (WeChat, Feishu, DingTalk, Telegram, WhatsApp)
Computer Use permission (once authorized) allowing the agent to take screenshots, click, type, and control desktop apps
A 'skip permissions' mode is available among the five permission levels, letting the agent run commands and tool calls without per-action approval

Risks and side effects

Computer Use can directly control the desktop once authorized; an overly permissive permission mode raises the chance of unintended actions
The app stores API keys for multiple model providers locally, concentrating sensitive credentials on one device
The skill marketplace allows installing third-party skills from ClawHub/SkillHub; source and safety status are shown, but supply-chain risk remains
Unsigned draft or temporary builds require manual one-time approval to run, which can be risky if the build source isn't trusted
As an MCP client, it can be pointed at arbitrary third-party MCP servers, so users must independently vet the trustworthiness of any server they add

Troubleshooting

On macOS, a one-time manual approval prompt usually indicates a draft or unsigned temporary build — see the desktop install guide
On Windows, if SmartScreen blocks the installer, click 'More info' then 'Run anyway'
When running from source, confirm bun install completed and .env is configured correctly (see the environment variables doc)
If model calls fail, check the model provider, API key, and default model settings in the app's Settings panel
For a specific MCP server connection issue, check that server's scope (project/shared/global) and transport configuration in the visual MCP manager

Use cases

Managing multiple Claude Code / coding-agent sessions on the desktop with tabs, project switching, and session history

Launching tasks against a Git branch or an isolated Worktree, then reviewing changes file by file as syntax-highlighted diffs

Adding and editing third-party MCP servers (STDIO/SSE/Streamable HTTP) through the built-in visual MCP manager

Continuing or approving running tasks remotely via Feishu, Telegram, WeChat, DingTalk, WhatsApp, or a phone H5 page

Letting an authorized agent take screenshots, click, and type to control desktop apps via Computer Use

Supported clients

Supported clients have not been confirmed yet.

Related MCP servers

Compare with other MCP servers