Yocoolab

MCP开发工具

提供方 Yocoolab · 包名 @yocoolab/mcp-server

开发工具 stdio · 本地进程 Token 社区 / 第三方 ClaudeCursorWindsurfCline
查看接入方式

MCP server for AI Agents — exposes Yocoolab feedback threads and design selections as tools

一句话选型结论

按资料字段整理

Yocoolab 属于开发工具类 MCP 服务器,stdio · 本地进程,Token,可直接接入 Claude、Cursor、Windsurf 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式stdio · 本地进程 鉴权Token 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 6 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量6暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

mcpmodel context protocolai agents

安装与配置

stdio · 本地进程 Token
客户端在本机拉起子进程,数据不出本机
npx -y @yocoolab/mcp-server@2 setup

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 node,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 6 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 6 个工具,职责相对集中,接入后不容易误操作。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude、Cursor、Windsurf,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Yocoolab当前 6 stdio · 本地进程 本地部署 有 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方Yocoolab上游标注的维护方 Yocoolab
分类开发工具本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式Token远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时@yocoolab/mcp-server · node本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

8.8 KB
来自项目仓库与上游目录的原文,未做删改

@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:```bash
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**.

**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:```bash
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:```bash
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:```json
{
  "mcpServers": {
    "yocoolab": {
      "command": "npx",
      "args": ["-y", "@yocoolab/mcp-server@3"],
      "env": {
        "YOCOOLAB_API_URL": "https://app.yocoolab.com",
        "YOCOOLAB_TOKEN": "<your-yocoolab-jwt>",
        "GITHUB_TOKEN": "<your-github-pat>",
        "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:
1. **Auto-detect (easiest):** install the GitHub CLI and run `gh auth login`. The server picks up the token automatically.
2. **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```bash
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.

License

Apache 2.0 — © 2026 Yocoolab

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Yocoolab 怎么安装?

在客户端按下面的安装命令接入:npx -y @yocoolab/mcp-server@2 setup。对应的包名是 @yocoolab/mcp-server。装完在客户端配置里引用同一个包或端点。

Yocoolab 怎么在 Claude、Cursor、Windsurf 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Yocoolab 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Yocoolab 需要 API Key 吗?

资料标注需要Token认证,使用前准备好对应凭据,并按最小权限配置。

Yocoolab 支持哪些客户端?

资料标注支持 Claude、Cursor、Windsurf、Cline、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Yocoolab 能提供哪些能力?

资料显示约 6 个工具;能力标签包括 mcp、model context protocol、ai agents、claude code、cursor、windsurf。具体工具清单以官方文档为准。

Yocoolab 需要什么运行环境?

运行时为 node;属于本地进程,需要在本机装好运行环境。

Yocoolab 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。