Skip to main content
Glama
1sarthakbhardwaj

Labellerr MCP Server

Related Servers

Alternatives to Labellerr MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server built with the mcp-framework for developing and managing custom tools. It provides a structured foundation for building and integrating modular components like data processors and API clients into Claude Desktop.
      2 npm
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server built with mcp-framework that allows users to create and manage custom tools for processing data, integrating with the Claude Desktop via CLI.
      20 npm
      5
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that allows integration with Claude Desktop by creating and managing custom tools that can be executed through the MCP framework.
      78 npm
      -
    • A
      license
      B
      quality
      C
      maintenance
      A model context protocol server that enables applications to use stackzero-labs/ui components through the MCP protocol, supporting both standalone operation and integration with Claude Desktop and Cursor.
      12
      65 npm
      5
      MIT

    TDQS

    C2.9/5.0

    Scored across 22 tools

    Disambiguation2/5

    Several tools have overlapping purposes: dataset_get and query_dataset_info both retrieve dataset details, while monitor_project_progress and query_project_statistics both provide project progress stats. project_list and query_search_projects also overlap in listing projects. This creates ambiguity for agents selecting the right tool.

    Naming Consistency3/5

    Naming is grouped by prefixes like project_, dataset_, annotation_, monitor_, query_, but the convention varies: some groups use resource_first (project_list, dataset_get) while others use action_first (monitor_job_status, query_project_statistics). Within each group it's consistent, but across groups the pattern is mixed, making it moderately predictable.

    Tool Count3/5

    With 22 tools, the count is on the heavier side. The scope covers projects, datasets, annotations, monitoring, and queries, so it isn't unreasonable, but it's borderline compared to the typical 3-15 tool range for a well-scoped server. Some tools are redundant, further padding the count.

    Completeness3/5

    The server covers core workflows for projects, datasets, and annotations, including creation, retrieval, uploading, and export. However, it lacks basic delete operations (e.g., no project delete or dataset delete) and has no annotation listing or detailed annotation viewing. The duplication of dataset info and project stats tools also suggests incomplete integration of the query and monitor groups.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues