yougile-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YG_CONFIRM | No | true requires confirm: true on every mutating tool call. | false |
| YG_LOG_FILE | No | If set, also appends log lines to this file (in addition to stderr). | |
| YG_READONLY | No | true blocks all mutating tools (_create/_update/_comment) — watch-only mode. | false |
| YG_LOG_LEVEL | No | Log verbosity: DEBUG, INFO, WARNING, ERROR. | INFO |
| YG_LOG_BODIES | No | true logs raw request/response bodies. | false |
| YOUGILE_API_KEY | No | Fallback API key used if none is stored yet in config.json. | |
| YOUGILE_BASE_URL | No | YouGile API base URL (for self-hosted/regional instances). | https://ru.yougile.com/api-v2 |
| YOUGILE_MCP_CONFIG_DIR | No | Directory where config.json (stored API key/company/base URL) lives. | ~/.yougile-mcp |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| yg_auth_statusA | Show YouGile auth status: whether an API key is stored and which company (if known). |
| yg_setupA | Store a YouGile API key (create one in the YouGile UI, or use yg_auth_create_key). Optionally set a custom base URL for self-hosted instances. |
| yg_auth_companiesB | List YouGile companies for a login/password so you can pick a companyId. Credentials are used once and NOT stored. |
| yg_auth_create_keyC | Create (or reuse) a YouGile API key for a company from login/password, and store it. Credentials are used once and NOT stored. |
| yg_projects_listB | List projects. Filter by title; paginate with limit/offset. |
| yg_project_createC | Create a project. |
| yg_boards_listB | List boards. Filter by projectId/title. |
| yg_board_createC | Create a board inside a project. |
| yg_columns_listB | List columns. Filter by boardId/title. |
| yg_column_createC | Create a column on a board. |
| yg_employees_listA | List company employees/users. Filter by email or projectId. Use to resolve assignee ids. |
| yg_tasks_listA | List tasks (the workhorse for watching). Server filters: columnId, title, includeDeleted, limit, offset. Client filters applied to the page: assignedTo (user id), completed, archived, deadlineBefore (ms epoch or ISO), changedAfter (ms epoch or ISO, vs task timestamp). |
| yg_task_getA | Get one task by id (full card). |
| yg_task_createC | Create a task in a column. |
| yg_task_updateA | Update a task: move (columnId), assign, deadline, complete, archive, edit title/description. Only provided fields change. Pass deadline=null to clear. |
| yg_task_chat_getB | Read the chat/comments of a task (chatId = task id). Useful for watching discussion. |
| yg_task_commentC | Post a comment to a task's chat. |
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 17 tools
Each tool maps to a distinct resource-action pair: auth setup, companies, projects, boards, columns, employees, tasks, and task chat. There is no meaningful overlap even within the auth cluster because each tool handles a different step or data source.
The yg_ prefix and the general resource_action pattern are consistently used, and plural list verbs are separated from singular create/get/update verbs. Minor deviations such as yg_setup, yg_auth_status, and yg_auth_companies (which lacks an explicit verb) keep it from being a perfect 5.
Seventeen tools is reasonable for a project management MCP server, covering authentication, projects, boards, columns, employees, tasks, and comments. The count feels intentional rather than bloated, and every tool has a clear role in the workflow.
The task lifecycle is well covered with list/get/create/update plus chat and comments, and project/board/column creation supports the hierarchy. Missing update/delete operations for projects, boards, and columns are minor gaps for a tool set primarily aimed at task monitoring and management.