Skip to main content
Glama
Yocoolab

@yocoolab/mcp-server

by Yocoolab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @yocoolab/mcp-server

No user-submitted related servers found.

    Related Servers

    • AI-Canvas MCP Server

      laoluojuhai
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to inspect, modify, export, and validate design documents with 47 tools covering design, code generation, branding, and print/mockup workflows.
      1 npm
      1
      MIT

    • Claude Talk to Figma MCP

      stranyer
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants like Claude and Cursor to interact directly with Figma to create, modify, and analyze design elements in real-time. It provides a comprehensive suite of tools for document inspection, styling, component management, and automated layout via a bidirectional WebSocket connection.
      202 npm
      MIT

    • Browser Feedback MCP

      itk-dev
      F
      license
      A
      quality
      A
      maintenance
      Enables visual browser feedback collection directly into Claude Code. Users can point at elements in their browser and send annotated feedback that Claude can act on immediately.
      12
      1
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 10 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources