YouGile Secure MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YOUGILE_API_KEY | Yes | Your YouGile API key |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_userA | Get the user profile that owns the configured YouGile API key. |
| list_projectsA | List projects visible to the configured YouGile API key. Returns items plus has_more; limit is capped at 100, use offset to fetch the next page. |
| get_projectA | Get one project by its YouGile UUID. |
| list_boardsA | List boards, optionally narrowed to a project. Returns items plus has_more; limit is capped at 100. |
| get_boardB | Get one board by its YouGile UUID. |
| list_columnsA | List columns, optionally narrowed to a board. Returns items plus has_more; limit is capped at 100. |
| list_tasksA | List tasks with server-side filters. Returns compact task summaries plus has_more (use get_task for the full object); limit is capped at 100. assigned_to accepts comma-separated user UUIDs. |
| get_taskA | Get one task with all fields by its YouGile UUID. |
| find_task_by_short_idA | Find a task by its human-readable ID such as ID-484 (company-wide) or DEV-484 (project). Scans the task list, so it may be slow on large workspaces; prefer get_task when the UUID is known. |
| list_task_commentsA | List chat messages (comments) of a task, oldest first. Returns items plus has_more; limit is capped at 100. |
| list_usersA | List company users, optionally filtered by project or email. Returns items plus has_more; limit is capped at 100. |
| list_string_stickersA | List custom stickers with their states, optionally narrowed to a board. Needed to decode task sticker values. Returns items plus has_more; limit is capped at 100. |
| propose_task_createA | Stage the creation of a task and get an approval token. Does NOT create anything: show the preview to the user, and only after the user explicitly approves call apply_approved_action with the token. |
| propose_task_updateA | Stage an update of an existing task and get an approval token. Does NOT change anything: show the preview to the user, and only after the user explicitly approves call apply_approved_action with the token. Allowed change fields: archived, assigned, checklists, color, columnId, completed, deadline, description, stickers, subtasks, timeTracking, title. Deleting tasks is not supported. |
| apply_approved_actionA | Execute a previously staged write action after the user explicitly approved it in chat. Requires the single-use approval token returned by a propose_* tool. |
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 15 tools
Each tool targets a distinct resource or action. Read tools (get_*, list_*) are separate from write tools (propose_*, apply_approved_action). The find_task_by_short_id is unique. No overlapping purposes.
All tool names use lower_snake_case and follow a verb_noun pattern. Verbs are consistently get_, list_, find_, propose_, apply_. No mixing of conventions.
15 tools is appropriate for a project management server. It covers listing and getting all major entities, plus a safe write pattern, without being excessive or too sparse.
Covers reading all entities and creating/updating tasks with a safe approval pattern. Missing delete for tasks and modifications for boards/columns/projects, but these are reasonable omissions given the secure nature.