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
} |
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 and this session's permissions. 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 default project from .yougile.json, else the whole company. |
| yougile_taskA | Open a task card: where it is, status, assignees, deadline, hours, checklists, stickers by name, description, and optionally the latest chat messages. |
| yougile_create_taskC | Create a task using names: board and column, assignees by name or email, deadline as a date, planned hours and a checklist. |
| yougile_update_taskA | Edit a task: title, description, assignees (by name), deadline, planned hours, completion, archive, color, checklist items. Only the given fields change. |
| yougile_move_taskB | Move a task to another column. On boards with a Workflow chain configured in .yougile.json the card is walked through every intermediate column, since YouGile rejects jumps over the chain. |
| 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_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 |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
The set mixes high-level convenience tools (yougile_find_tasks, yougile_update_task, yougile_task_chat) with generic resource tools exposing operations (yougile_tasks, yougile_chats), creating multiple overlapping paths for retrieving and updating tasks. The descriptions help clarify intent, but an agent could easily hesitate between the convenience layer and the operations layer.
All tools share a consistent yougile_ snake_case prefix, and most action tools follow a verb_noun pattern while resource tools use plain plural nouns. Minor inconsistencies like singular yougile_task vs plural yougile_tasks, plus yougile_overview and yougile_log_time, keep it from being perfectly uniform.
19 tools is at the upper end of the recommended range, but the server covers a broad domain spanning tasks, projects, boards, columns, chats, users, stickers, files, and CRM. The count feels slightly heavy due to convenience/resource duplication, but each tool addresses a real part of the YouGile workspace.
The tool surface provides solid lifecycle coverage for the core domain: projects, boards, columns, tasks, chats, users, stickers, and company settings. Task search, creation, update, moving, time logging, checklists, archiving, and soft-delete are all represented, so there are no obvious dead ends for typical project management workflows.