@yocoolab/mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub PAT with repo scope. Auto-detected if gh CLI is installed and authenticated. | |
| YOCOOLAB_TOKEN | No | Your Yocoolab JWT (from the Chrome extension). When unset, thread feedback tools are disabled but bridge / companion / activity tools still work. | |
| YOCOOLAB_API_URL | No | Yocoolab API base URL | https://app.yocoolab.com |
| YOCOOLAB_AGENT_NAME | No | Display name shown in the Chrome extension's agent picker | Claude Code |
| YOCOOLAB_AGENT_TYPE | No | Agent type identifier (claude-code, roo, cline, cursor, windsurf, or custom) | claude-code |
| YOCOOLAB_BRIDGE_PORT | No | Local port for the HTTP bridge to the Chrome extension | 9800 |
| YOCOOLAB_BRIDGE_WORKSPACE | No | Absolute path to your project workspace, used to resolve file references in selections | process.cwd() |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_companion_messagesA | 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. |
| reply_to_companionA | 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_selectionA | 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_historyA | Returns the last N element selections from the Chrome extension, newest first. Useful for comparing multiple elements or reviewing recent selections. |
| find_source_for_selectionA | 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. |
| get_element_contextA | 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. |
| get_activity_summaryA | Get a high-level summary of Claude Code activity: total events, active sessions, tool usage breakdown, files touched, and error count. |
| get_recent_eventsA | Get the most recent Claude Code activity events (tool calls, prompts, errors). Shows timestamps, tool names, and key details. |
| get_files_touchedA | List all files that have been read, written, or edited across Claude Code sessions. Shows file paths with session counts. |
| get_dashboard_urlA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose: selection handling, source finding, element context, companion messaging, activity monitoring, and dashboard URL. Even similar tools like get_latest_selection and get_selection_history differ by scope (single vs. history). No overlap that would cause confusion.
All tools follow a verb_noun pattern with underscores (e.g., get_activity_summary, find_source_for_selection). While most use 'get', two use 'find' and 'reply', which is a minor deviation from a uniform verb prefix. Overall pattern is consistent and predictable.
With 10 tools, the server is well-scoped for its purpose of combining UI element inspection and Claude Code activity monitoring. Each tool serves a clear role without unnecessary bloat or deficiency.
The tool surface covers the key workflows: selecting elements, getting context, finding source code, companion chat, and activity monitoring. Minor gaps exist, such as no tool to clear selection history or reset companion state, but these are not critical for the core use case.