
Pin visual feedback on any live web page and send it to Claude Code, Cursor or your AI agent.
Pin visual feedback on any live web page and send it to Claude Code, Cursor or your AI agent.
·
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:
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/mcpThen 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:
curl -fsSL https://app.yocoolab.com/agent/install.sh | shSwitching 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.
One command:
npx -y @yocoolab/mcp-server@3 setupThe 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.
initis kept as an alias forsetupfor 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": "<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.
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.| 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 <your GitHub PAT> 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) |
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 helpThe mcp-server command is a synonym for yocoolab-mcp. Either works.
The server exposes tools across several categories:
list_open_threads, get_thread_context, add_thread_message, mark_thread_addressed, create_pr_for_thread
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.get_latest_selection, get_selection_history, get_element_context, find_source_for_selection, ai_analyze_pageget_companion_messages, reply_to_companionget_ai_conversationsget_deployment_previewpendo_list_guides, pendo_page_analytics, pendo_feature_usage, pendo_track_eventFor full tool descriptions and parameters, your MCP client will list them after the server starts.
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:
gh auth login. The server picks up the token automatically.repo scope and add GITHUB_TOKEN: "ghp_..." to your MCP config's env block.
If your config has a placeholder value like <your GitHub PAT>, the server detects it and shows a helpful message instead of crashing with a 401.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 --watchSee CONTRIBUTING.md for the full contributor workflow.
npm audit signatures and CodeQL static analysis in CI on every PR.Apache 2.0 — © 2026 Yocoolab
Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add yocoolab -- npx -y @yocoolab/mcp-server@3{
"mcpServers": {
"yocoolab": {
"env": {
"GITHUB_TOKEN": "",
"YOCOOLAB_TOKEN": "",
"YOCOOLAB_API_URL": "",
"YOCOOLAB_BRIDGE_PORT": "",
"YOCOOLAB_BRIDGE_WORKSPACE": ""
},
"args": [
"-y",
"@yocoolab/mcp-server@3"
],
"command": "npx"
}
}
}code --add-mcp '{"name":"yocoolab","env":{"GITHUB_TOKEN":"","YOCOOLAB_TOKEN":"","YOCOOLAB_API_URL":"","YOCOOLAB_BRIDGE_PORT":"","YOCOOLAB_BRIDGE_WORKSPACE":""},"args":["-y","@yocoolab/mcp-server@3"],"command":"npx"}'[mcp_servers.yocoolab]
command = "npx"
args = ["-y", "@yocoolab/mcp-server@3"]Runs locally on your device. Your client starts the server itself, so nothing has to be hosted.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/mcp-server-2 to learn what the "Mcp Server" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
claude mcp add --transport http --scope user yocoolab https://app.yocoolab.com/mcpnpx -y @yocoolab/mcp-server@3 setup| Name | What it does |
|---|---|
get_companion_messages | Check for new messages from the AI Companion panel in the Chrome extension. Returns pending messages and clears the queue. Each message includes the user text, page context, and optional screenshot/el |
reply_to_companion | Send a reply back to the AI Companion panel in the Chrome extension. The reply will appear as an assistant message in the companion chat UI. Supports Markdown formatting. |
get_latest_selection | Returns the most recent element selection from the Chrome extension. Includes element selector, tag, text content, classes, attributes, computed styles, and page context. |
get_selection_history | Returns the last N element selections from the Chrome extension, newest first. Useful for comparing multiple elements or reviewing recent selections. |
find_source_for_selection | Searches the workspace for source files that likely define or render the selected UI element. Returns ranked candidates with file paths, line ranges, confidence scores, and match reasons. Can work wit |
get_element_context | Returns a comprehensive summary of a UI element, including its DOM context, computed styles, and ranked source code candidates. Works with live Chrome selections or stored thread element_context. This |
Read live from the server on October 7, 2026.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/mcp-server-2)Nothing comparable is listed yet.
v2.2.1Release notesv2.2.0Release notesv2.1.1Release notesv2.1.0Release notesv2.0.0Release notesConnect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "mcp-server-2" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.