Yocoolab

Name: Yocoolab
Author: Yocoolab

by Yocoolabversion 3.0.0i★ –iRuns on your computer

Registry nameio.github.Jonahbkerr/yocoolab

Install

Overview

Description from the maker (original English)

Pin visual feedback on any live web page and send it to Claude Code, Cursor or your AI agent.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi0 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Web & browsers
You need to fill in: YOCOOLAB_TOKEN, GITHUB_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 0 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: YOCOOLAB_TOKEN, YOCOOLAB_API_URL, GITHUB_TOKEN, YOCOOLAB_BRIDGE_WORKSPACE

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "yocoolab": {
      "command": "npx",
      "args": [
        "-y",
        "@yocoolab/mcp-server"
      ],
      "env": {
        "YOCOOLAB_TOKEN": "your-value",
        "YOCOOLAB_API_URL": "your-value",
        "GITHUB_TOKEN": "your-value",
        "YOCOOLAB_BRIDGE_WORKSPACE": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add yocoolab --env YOCOOLAB_TOKEN=your-value --env YOCOOLAB_API_URL=your-value --env GITHUB_TOKEN=your-value --env YOCOOLAB_BRIDGE_WORKSPACE=your-value -- npx -y @yocoolab/mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "yocoolab": {
      "command": "npx",
      "args": [
        "-y",
        "@yocoolab/mcp-server"
      ],
      "env": {
        "YOCOOLAB_TOKEN": "your-value",
        "YOCOOLAB_API_URL": "your-value",
        "GITHUB_TOKEN": "your-value",
        "YOCOOLAB_BRIDGE_WORKSPACE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "yocoolab": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@yocoolab/mcp-server"
      ],
      "env": {
        "YOCOOLAB_TOKEN": "your-value",
        "YOCOOLAB_API_URL": "your-value",
        "GITHUB_TOKEN": "your-value",
        "YOCOOLAB_BRIDGE_WORKSPACE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

YOCOOLAB_TOKEN secret env
Your Yocoolab JWT, from the Chrome extension settings or app.yocoolab.com. When unset, thread feedback tools are disabled but bridge, companion and selection tools still work.
YOCOOLAB_API_URL env
Yocoolab API base URL. Defaults to https://app.yocoolab.com.
GITHUB_TOKEN secret env
GitHub PAT with repo scope, needed only for the PR-creation tools. Auto-detected from the gh CLI when authenticated.
YOCOOLAB_BRIDGE_WORKSPACE env
Absolute path to your project workspace, used to resolve file references in selections. Defaults to the current working directory.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

! Caution
Maker matches the repo
The publisher (Jonahbkerr) is not the repo owner (Yocoolab); someone else may have listed it
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Web & browsersi

More stars than 0% of the other 881 servers in this category
Published to the registry more recently than 52% of the other 881 servers in this category
Basic checks equal to or better than 23% of the other 881 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Yocoolab safe?

It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: YOCOOLAB_TOKEN, GITHUB_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (3.0.0) reached the registry 35 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Browser Use

by browser-use

Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.

Computer or cloud★ 120,087MITUpdated 17 days ago

Install

Chrome DevTools MCP

by ChromeDevTools

Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.

Runs on your computer★ 54,821Apache-2.0Updated 16 days ago

Install

MCP Server Browser

by bytedance

MCP server for browser use access

Runs on your computer★ 39,550Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@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

Recommended: the hosted Yocoolab MCP (nothing to install)

Most people no longer need this package. Yocoolab hosts the MCP server at `https://app.yocoolab.com/mcp`. Your agent signs in to Yocoolab in the browser the first time, so there is no token to paste:

claude mcp add --transport http --scope user yocoolab https://app.yocoolab.com/mcp

Then type /mcp in Claude Code, choose yocoolab, and Authenticate. Setup for Cursor, VS Code, the Claude app, and headless agents (agent token in a header) is at [app.yocoolab.com/connect](https://app.yocoolab.com/connect).

Always-on agent: to have one computer pick up every Send to Agent in your workspace by itself (it runs Claude Code), run this on that computer:

curl -fsSL https://app.yocoolab.com/agent/install.sh | sh

Switching from this package to the hosted server? Remove the old entry first (claude mcp remove yocoolab, repeat until none is found). Otherwise Claude may keep using the old one.

Use this package only if you need what runs on your own machine: the local bridge on :9800 for live selections from the Chrome extension.

Install (local package)

One command:

npx -y @yocoolab/mcp-server@3 setup

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:

"mcpServers": { "yocoolab": { "command": "npx", "args": ["-y", "@yocoolab/mcp-server@3"], "env": { "YOCOOLAB_API_URL": "https://app.yocoolab.com", "YOCOOLAB_TOKEN": " ", "GITHUB_TOKEN": " ", "YOCOOLAB_BRIDGE_PORT": "9800", "YOCOOLAB_BRIDGE_WORKSPACE": "/absolute/path/to/your/workspace" } } } }

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`)

CLI

yocoolab-mcp           Run the MCP server (used by your agent via .mcp.json)

yocoolab-mcp setup Interactive setup — auto-detects agents and writes their configs yocoolab-mcp init Alias for setup (backwards compatible with v1.0.x) yocoolab-mcp --help Show this help

The mcp-server command is a synonym for yocoolab-mcp. Either works.

Tools

The server exposes tools across several categories:

Threads — list_open_threads, get_thread_context, add_thread_message, mark_thread_addressed, create_pr_for_thread
On a link-only project (no GitHub App connection) open the PR with your own git/gh, then call mark_thread_addressed with pr_url (and pr_branch, preview_url when you have them). The PR fields land on the thread and the preview link goes into the review message; get_thread_context prints the project's repo links so you know which repository it points at. create_pr_for_thread remains for GitHub-connected owner/name workspaces.
Selection / Bridge — get_latest_selection, get_selection_history, get_element_context, find_source_for_selection, ai_analyze_page
Companion — get_companion_messages, reply_to_companion
AI — get_ai_conversations
Deployment — get_deployment_preview
Pendo (optional) — pendo_list_guides, pendo_page_analytics, pendo_feature_usage, pendo_track_event

For full tool descriptions and parameters, your MCP client will list them after the server starts.

Troubleshooting

`yocoolab-mcp: command not found` — make sure you're on v1.0.1 or newer. Run npx -y @yocoolab/mcp-server@latest setup to get the current release.

`[yocoolab] Warning: YOCOOLAB_TOKEN not set` — thread feedback tools are disabled without a token, but bridge / companion / selection tools still work. To enable everything, run yocoolab-mcp setup to (re)generate the config with your JWT.

Tools don't appear in your agent after install — restart your agent completely (quit & reopen). MCP servers load at startup.

`Port 9800 is already in use` — another instance of the MCP server is running, or another app has the port. Set YOCOOLAB_BRIDGE_PORT to a different value (e.g. 9801) in your .mcp.json.

Verbose diagnostic logs — set DEBUG=yocoolab:* in your env block. All diagnostic output goes to stderr (so it doesn't interfere with the MCP stdio protocol on stdout).

PR creation says "GitHub token not configured" — the create_pr_for_thread tool needs a GitHub token. Two ways to fix:

Auto-detect (easiest): install the GitHub CLI and run gh auth login. The server picks up the token automatically.
Manual: create a personal access token with repo scope and add GITHUB_TOKEN: "ghp_..." to your MCP config's env block.

If your config has a placeholder value like , the server detects it and shows a helpful message instead of crashing with a 401.

Support

Documentation: this README, plus inline tool descriptions visible in your MCP client
Bug reports: github.com/Yocoolab/mcp-server/issues (use the bug template)
Security issues: see SECURITY.md — do not open a public issue
Other questions: support@yocoolab.com

Development

git clone https://github.com/Yocoolab/mcp-server.git

cd mcp-server npm install npm run build # compile TypeScript to dist/ npm test # run the vitest suite npm run dev # tsc --watch

See CONTRIBUTING.md for the full contributor workflow.

Security & supply chain

Released with npm provenance — every published version is cryptographically signed by GitHub Actions OIDC, traceable back to the exact commit and workflow run.
Each release ships with a CycloneDX SBOM attached to the GitHub Release.
We run npm audit signatures and CodeQL static analysis in CI on every PR.
See SECURITY.md for vulnerability reporting.

Yocoolab

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Web & browsersi

Common questions

Alternatives

Browser Use

Chrome DevTools MCP

MCP Server Browser

README from the maker

@yocoolab/mcp-server

Recommended: the hosted Yocoolab MCP (nothing to install)

Install (local package)

Requirements

Configuration

CLI

Tools

Troubleshooting

Support

Development

Security & supply chain

License