@yocoolab/mcp-server

List open feedback threads. Omit repo to get ALL threads across every repo you have access to — each result is labeled with its repo, change type (frontend/api/backend), board stage, and UI element context. Use claude_code_pending=true to only show threads that users have sent to Claude Code.

Get full details of a feedback thread including all messages, UI element context (selector, coordinates, element tag), view state, and the annotated screenshot. The screenshot is returned as an image so you can visually see the feedback location.

Create a GitHub pull request (or add a commit to the existing working branch) with code changes that address a feedback thread. All fixes for a repo accumulate on a single working branch with one PR.

Mark a feedback thread as addressed and ready for review. This moves the thread to the

Check if a preview deployment is available for a specific repo and branch. Returns the preview URL if deployed. Useful after creating a PR to get the live preview link.

Add a message to a feedback thread without changing its status. Use this to post updates like preview URLs, implementation notes, or questions back to the thread.

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/element attachments.

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.

Ask the Yocoolab AI assistant to analyze a web page. Supports text questions with optional screenshot (vision) and page context. Useful for getting AI insights about a page layout, accessibility, or code structure.

List recent AI assistant conversations. Returns conversation IDs, page URLs, and message counts.

Query Pendo for feature usage analytics (click events, unique visitors) over a time range. Useful for understanding how heavily a feature is used when reviewing feedback threads.

Query Pendo for page-level analytics (page views, unique visitors, avg time on page). Use the page_url from thread context to check how popular a page is.

Send a custom track event to Pendo. Use this to track actions like feedback resolved, PR created from feedback, or guide suggestions.

List active in-app guides from Pendo. Optionally filter by page URL to see what guides are deployed on a specific page.

Get a high-level summary of Claude Code activity: total events, active sessions, tool usage breakdown, files touched, and error count.

Get the most recent Claude Code activity events (tool calls, prompts, errors). Shows timestamps, tool names, and key details.

List all files that have been read, written, or edited across Claude Code sessions. Shows file paths with session counts.

Get the URL for the real-time activity monitoring dashboard. Open in a browser to see live Claude Code activity, tool usage charts, and session timelines.

Returns the last N element selections from the Chrome extension, newest first. Useful for comparing multiple elements or reviewing recent selections.

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 with live Chrome selections or stored thread 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 is the primary tool to use when the user wants to modify a UI element.

Returns the most recent element selection from the Chrome extension. Includes element selector, tag, text content, classes, attributes, computed styles, and page context.