YouGile MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YOUGILE_CONFIG | No | Explicit path to a config file instead of looking for .yougile.json. | |
| YOUGILE_API_KEY | Yes | API key for YouGile, required to run the server. | |
| YOUGILE_BASE_URL | No | Address of the YouGile server, e.g., your on-premise server. | https://ru.yougile.com |
| YOUGILE_TIMEZONE | No | Company time zone, overrides 'timezone' from the config file. | Europe/Moscow |
| YOUGILE_RATE_LIMIT | No | Requests per minute per key; 0 disables the limiter. | 45 |
| YOUGILE_MCP_LOG_LEVEL | No | Log level; logs go to stderr. | WARNING |
| YOUGILE_MCP_STATE_DIR | No | Directory where the shared rate-limit counter lives. Defaults to OS cache dir. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| yougile_overviewA | Company structure: projects -> boards -> columns in screen order, Workflow chains, workspace defaults, columns that count as done, this session's permissions and where settings are changed. Start here to learn the names. |
| yougile_find_tasksA | Find tasks by project/board/column names, assignee and title words. Without a place, searches the workspace's default project if one is set, else the whole company. Completed tasks show completed_at; tasks in a column that counts as done but not marked completed show done_by_column: true (YouGile keeps no date for those); open tasks past their deadline show overdue: true. completed_since/completed_until select tasks completed in a period, newest first. |
| yougile_taskA | Open a task card: where it is, status, assignees, deadline, hours, checklists, stickers by name, description, and optionally the latest chat messages. Stickers of types the YouGile API does not describe (numbers, free text) come by id under other_stickers. |
| yougile_create_taskA | Create a task using names: board and column, assignees by name or email, deadline as a date, planned hours and a checklist. For client work in a company with client copies, pass client_title and client_description to create the client copy too (see yougile_client_copy). |
| yougile_update_taskA | Edit a task: title, description (replace it, or append to it), assignees (by name), deadline, planned hours, completion, archive, color, checklist items. Only the given fields change. |
| yougile_move_taskA | Move a task to another column. On boards with a configured Workflow chain (shown by yougile_overview) the card is walked through every intermediate column, since YouGile rejects jumps over the chain. Moving into a column that counts as done marks the task completed (so YouGile records the date); moving it back out reopens it. |
| yougile_log_timeA | Add worked hours to a task's time tracking (plan/work), keeping the plan. |
| yougile_task_chatA | Read the latest messages of a task's chat, optionally posting a message first. |
| yougile_attach_fileA | Attach a file to a task: upload it to YouGile and post it into the task's chat, where it shows as an attachment, optionally after a comment. Pass file_path, or content_base64 with filename. |
| yougile_use_boardA | Remember the board the user usually works on: task tools use it whenever they get neither a board nor a project (creating a task, a column without a board). Call it when the user says which board they work on or asks to remember it. Nothing changes in YouGile. |
| yougile_tasksB | YouGile tasks: list/search (filters: columnId, assignedTo, stickerId, title), get by UUID or by number like ID-123, create, update (move via columnId, complete, archive, deadline, timeTracking plan/work hours, checklists, stickers, soft-delete via deleted=true), task chat subscribers. A task's chat id equals the task id (see yougile_chats). Operations ([access]):
Call yougile_help('tasks.') for parameters. |
| yougile_chatsB | Chat messages of tasks (chatId = task id) and group chats: history, send, edit/delete, reactions; group chat management. Operations ([access]):
Call yougile_help('chats.') for parameters. |
| yougile_boardsB | Boards: list (by projectId), get, create, update/rename/move/soft-delete. Operations ([access]):
Call yougile_help('boards.') for parameters. |
| yougile_columnsB | Board columns: list (by boardId), get, create, update/rename/soft-delete. Operations ([access]):
Call yougile_help('columns.') for parameters. |
| yougile_projectsC | Projects and project roles: list, get, create, update members, roles CRUD. Operations ([access]):
Call yougile_help('projects.') for parameters. |
| yougile_usersB | Company employees and departments: list, get, me, invite, update, remove. Operations ([access]):
Call yougile_help('users.') for parameters. |
| yougile_stickersB | Custom stickers (string/state and sprint) and their states. Operations ([access]):
Call yougile_help('stickers.') for parameters. |
| yougile_companyC | Company details and webhooks (event subscriptions). Operations ([access]):
Call yougile_help('company.') for parameters. |
| yougile_filesA | Upload a file to YouGile; returns a URL to use in chat messages or descriptions. Operations ([access]):
Call yougile_help('files.') for parameters. |
| yougile_crmA | CRM: contact persons and lookup of contacts by external messenger id. Operations ([access]):
Call yougile_help('crm.') for parameters. |
| yougile_helpA | Describe YouGile domain tools and operations: parameters, types, required fields, access. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| standup | Что сделано со вчера, что в работе, блокеры. |
| hours_report | План и факт часов по задачам за период: по проектам, людям, перерасход. |
| triage | Задачи очереди без исполнителя, срока или оценки — и что с ними сделать. |
| client_sync | Какие задачи доски нужно показать клиенту, и их тексты для клиента. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Prefab Renderer (yougile_show_task) | |
| Prefab Renderer (yougile_show_tasks) | |
| Prefab Renderer (yougile_show_board) | |
| Prefab Renderer (yougile_new_task_form) | |
| Prefab Renderer (yougile_show_standup) | |
| Prefab Renderer (yougile_show_hours) | |
| Prefab Renderer (yougile_show_triage) | |
| Prefab Renderer (yougile_attach_files) |
TDQS
Scored across 21 tools
The tool set mixes high-level convenience tools (yougile_create_task, yougile_move_task, yougile_task_chat) with generic CRUD tools (yougile_tasks, yougile_chats) that cover the same operations. For example, yougile_create_task and yougile_tasks.create both create tasks, and yougile_task and yougile_tasks.get both retrieve task details. This overlap makes it ambiguous which tool an agent should select for a given action, despite descriptions that differentiate nuances.
Naming is inconsistent: some tools follow a verb_noun pattern (yougile_create_task, yougile_move_task, yougile_log_time), while others are plain resource names (yougile_tasks, yougile_chats, yougile_boards). There is also singular vs. plural inconsistency (yougile_task vs. yougile_tasks). This mixed convention makes it difficult to predict tool names for new operations.
21 tools is on the higher end but reasonable for a comprehensive project management server covering tasks, chats, boards, columns, projects, users, stickers, company, files, and CRM. The count is inflated by redundancy between high-level and low-level tools, but each tool has a distinct purpose within its layer, so the scope is justified.
The tool set covers the core lifecycle of YouGile: task creation, retrieval, update, move, time logging, chat, file attachment, and searching. It also includes CRUD for projects, boards, columns, users, stickers, company webhooks, and CRM. Missing explicit delete operations are handled via soft-delete flags in update tools, which is a minor gap but not a dead end.