Yocoolab/mcp-server

MCP (Model Context Protocol) server that exposes Yocoolab feedback threads and design selections as tools for Claude Code and other MCP-compatible clients.
With this installed, your AI coding assistant can:
- List and triage open design feedback threads on your repo
- Pull rich context for a thread (selection, screenshot, conversation, files touched)
- Reply to designers and mark threads as addressed
- Open PRs that close out feedback threads
- Inspect element context and selection history from the Yocoolab Chrome extension
- Read companion chat messages, AI conversations, and Pendo product analytics
Install
One command:
The setup wizard auto-detects your installed AI agents (Claude Code, Cursor, Cline, Roo Code, Windsurf) and writes the correct MCP config for each. Restart your agent and the yocoolab server appears with all tools available.
> init is kept as an alias for setup for backwards compatibility with v1.0.x install instructions.
If you'd rather configure manually, the equivalent ~/.mcp.json looks like:
The @3 version pin keeps you on the v3 major line — you'll receive bug fixes and new features automatically, but a future v4 with breaking changes won't break your setup. v3.0.0 removed the activity monitor and no longer writes Claude Code hooks into ~/.claude/settings.json; see CHANGELOG.md if you are upgrading from v2.
Requirements
- **Node.js 20 or newer.** We test on Node 20 and 22 in CI. We support whichever Node.js versions are currently in Active LTS or Maintenance LTS status, and drop versions within 30 days of their EOL. Node 18 was dropped in v2.0.0 (EOL April 2025).
- **A Yocoolab account and JWT token** — get yours from the Yocoolab Chrome extension settings, or via your account at app.yocoolab.com.
- **A GitHub personal access token** with repo scope, if you want to use the PR-creation tools (create_pr_for_thread). The token is auto-detected if you have the GitHub CLI installed and authenticated (gh auth login). No GITHUB_TOKEN env var needed in that case. Otherwise, create one at github.com/settings/tokens/new?scopes=repo.
Configuration
| Env var | Required | Default | Description |
|---|---|---|---|
| YOCOOLAB_TOKEN | no | — | Your Yocoolab JWT (from the Chrome extension). When unset, thread feedback tools are disabled but bridge / companion / selection tools still work. |
| YOCOOLAB_API_URL | no | https://app.yocoolab.com | Yocoolab API base URL |
| GITHUB_TOKEN | only for PR tools | — | GitHub PAT with repo scope. **Auto-detected** — if gh CLI is installed and authenticated (gh auth token), no env var is needed. Placeholder values like are detected and safely ignored. |
| YOCOOLAB_BRIDGE_PORT | no | 9800 | Local port for the HTTP bridge to the Chrome extension |
| YOCOOLAB_BRIDGE_WORKSPACE | no | process.cwd() | Absolute path to your project workspace, used to resolve file references in selections |
| YOCOOLAB_AGENT_NAME | no | Claude Code | Display name shown in the Chrome extension's agent picker |
| YOCOOLAB_PROJECT_PR_LINKS | no | 1 | Set to 0 to restore the pre-2.5 behaviour: mark_thread_addressed without PR/preview link fields, GitHub-only PR guidance in the prompt |
| YOCOOLAB_AGENT_TYPE | no | claude-code | Agent type identifier (claude-code, roo, cline, cursor, windsurf, or custom) |