@nebelov/yougile-mcp
Related Servers
Alternatives to @nebelov/yougile-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceMCP 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.5726 npm9MIT
- AlicenseBqualityAmaintenanceMCP server that exposes YouGile projects, boards, columns, tasks, and task chat as tools for agents to watch and manage tasks.1717 npmMIT
- FlicenseNot gradedqualityDmaintenanceIntegrates with YouGile to allow AI assistants to create, update, and manage projects, tasks, and team members via the MCP protocol.12-
- FlicenseCqualityDmaintenanceMCP server for the Zube.io project management API, exposing boards, cards, epics, tickets, sprints, and workspaces as tools for AI assistants.42-
- AlicenseBqualityDmaintenanceA production-grade Model Context Protocol server for YouGile that lets AI agents read and manage projects, boards, tasks, employees, and more.4410 npm2MIT
- AlicenseNot gradedqualityCmaintenanceA comprehensive Model Context Protocol server that provides AI agents with 44 tools to manage JetBrains YouTrack issues, sprints, and projects via the REST API. It supports full YouTrack query language and works with both Cloud and Server instances for complete project management integration.78 npmMIT
TDQS
Scored across 57 tools
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.
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.
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).
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.