Skip to main content
Glama

Related Servers

Alternatives to @nebelov/yougile-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      F
      maintenance
      MCP server for YouGile project management. Provides 57 tools covering 100% of YouGile API v2, enabling natural language management of projects, boards, columns, tasks, chats, users, and more.
      57
      65 npm
      10
      MIT
    • F
      license
      C
      quality
      D
      maintenance
      MCP server for the Zube.io project management API, exposing boards, cards, epics, tickets, sprints, and workspaces as tools for AI assistants.
      42
      -
    • A
      license
      B
      quality
      D
      maintenance
      A production-grade Model Context Protocol server for YouGile that lets AI agents read and manage projects, boards, tasks, employees, and more.
      44
      21 npm
      2
      MIT

    TDQS

    A3.5/5.0

    Scored across 57 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with clear prefixes like list/get/create/update/delete. Even similar sticker tools are differentiated by 'string' vs 'sprint' and 'state' sub-resource. No two tools appear to perform the same operation.

    Naming Consistency5/5

    All tools follow the consistent `yougile_<verb>_<noun>` pattern, using snake_case throughout. Verbs are standard (list/get/create/update/delete/set/invite/send), and nouns are singular for get/update and plural for list, which is conventional.

    Tool Count1/5

    With 57 tools, the server far exceeds the threshold for an extreme count (50+). While the domain is broad, this number creates a heavy cognitive load for agents and suggests over-fragmentation (e.g., separate string and sprint sticker tools could be unified).

    Completeness5/5

    The server provides full CRUD/lifecycle coverage for all major resources: projects, boards, columns, tasks, users, departments, roles, stickers, chats, messages, and webhooks. Soft-delete via update covers missing delete endpoints, and the API's lack of message editing is properly documented. No critical workflow dead ends are apparent.

    Maintenance

    ActivityStale
    ResponsivenessNo issues