yougile-mcp by Ivan Tereshin
yougile-mcp
A production-grade MCP server for YouGile: 44 full-CRUD tools, resources, ready prompts and two transports
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- Full CRUD over every company resource: projects, boards, tasks, users, departments and webhooks
- The API key grants access to the whole company; the server does not scope permissions by role or project
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/ivantereshin-yougile-mcpDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
This entry is high risk, so there is no one-click install. Review the code and add the config by hand.
Run in a terminal
claude mcp add --transport stdio --env 'YOUGILE_API_KEY=<your YOUGILE_API_KEY>' yougile -- npx -y yougile-mcpOr add to the file .mcp.json, in the project
{
"mcpServers": {
"yougile": {
"command": "npx",
"args": [
"-y",
"yougile-mcp"
],
"env": {
"YOUGILE_API_KEY": "<your YOUGILE_API_KEY>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
YOUGILE_API_KEYsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.cursor/mcp.json, for all projects
{
"mcpServers": {
"yougile": {
"command": "npx",
"args": [
"-y",
"yougile-mcp"
],
"env": {
"YOUGILE_API_KEY": "<your YOUGILE_API_KEY>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.
Keys and settings
YOUGILE_API_KEYsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Run in a terminal
code --add-mcp '{"name":"yougile","type":"stdio","command":"npx","args":["-y","yougile-mcp"],"env":{"YOUGILE_API_KEY":"<your YOUGILE_API_KEY>"}}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"yougile": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"yougile-mcp"
],
"env": {
"YOUGILE_API_KEY": "<your YOUGILE_API_KEY>"
}
}
}
}If the file already exists, add the server inside the servers key.
Keys and settings
YOUGILE_API_KEYsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Run in a terminal
codex mcp add yougile --env 'YOUGILE_API_KEY=<your YOUGILE_API_KEY>' -- npx -y yougile-mcpOr add to the file ~/.codex/config.toml, for all projects
[mcp_servers.yougile]
command = "npx"
args = ["-y", "yougile-mcp"]
env = { YOUGILE_API_KEY = "<your YOUGILE_API_KEY>" }If the file already exists, append the block to the end.
Keys and settings
YOUGILE_API_KEYsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"yougile": {
"command": "npx",
"args": [
"-y",
"yougile-mcp"
],
"env": {
"YOUGILE_API_KEY": "<your YOUGILE_API_KEY>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
YOUGILE_API_KEYsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.config/devin/mcp_config.json, for all projects
{
"mcpServers": {
"yougile": {
"command": "npx",
"args": [
"-y",
"yougile-mcp"
],
"env": {
"YOUGILE_API_KEY": "<your YOUGILE_API_KEY>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.
Keys and settings
YOUGILE_API_KEYsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Formerly Windsurf.
Add to the file cline_mcp_settings.json, for all projects
{
"mcpServers": {
"yougile": {
"command": "npx",
"args": [
"-y",
"yougile-mcp"
],
"env": {
"YOUGILE_API_KEY": "<your YOUGILE_API_KEY>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.
Keys and settings
YOUGILE_API_KEYsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file .roo/mcp.json, in the project
{
"mcpServers": {
"yougile": {
"command": "npx",
"args": [
"-y",
"yougile-mcp"
],
"env": {
"YOUGILE_API_KEY": "<your YOUGILE_API_KEY>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
YOUGILE_API_KEYsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
A fork of Roo Code, same .roo folders.
Add to the file opencode.json, in the project
{
"mcp": {
"yougile": {
"type": "local",
"command": [
"npx",
"-y",
"yougile-mcp"
],
"environment": {
"YOUGILE_API_KEY": "<your YOUGILE_API_KEY>"
}
}
}
}If the file already exists, add the server inside the mcp key.
Keys and settings
YOUGILE_API_KEYsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.config/zed/settings.json, for all projects
{
"context_servers": {
"yougile": {
"command": "npx",
"args": [
"-y",
"yougile-mcp"
],
"env": {
"YOUGILE_API_KEY": "<your YOUGILE_API_KEY>"
}
}
}
}If the file already exists, add the server inside the context_servers key.
Keys and settings
YOUGILE_API_KEYsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file .codeassistant/mcp.json, in the project
{
"mcpServers": {
"yougile": {
"command": "npx",
"args": [
"-y",
"yougile-mcp"
],
"env": {
"YOUGILE_API_KEY": "<your YOUGILE_API_KEY>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
YOUGILE_API_KEYsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Get an API key from YouGile → Settings → API, then add the server to claude_desktop_config.json with the command npx -y yougile-mcp and the YOUGILE_API_KEY variable.
Other ways from the author
{
"mcpServers": {
"yougile": {
"command": "npx",
"args": ["-y", "yougile-mcp"],
"env": { "YOUGILE_API_KEY": "your-key" }
}
}
}The README config for Claude Desktop; Cursor uses the same entry in .cursor/mcp.json.
This is third-party code. Review the repository files before installing.
What it does
The server provides full list, get, create and update (soft-delete via update) coverage of every core YouGile entity: projects, boards, columns, tasks, users, departments, group chats, string and sprint stickers, webhooks, plus task chat and company data. On top of the tools there are MCP resources yougile://projects, yougile://users and the yougile://board/{boardId} template, plus ready prompts triage_board, create_task_from_note, standup_report and find_stale_tasks. It runs over both stdio and Streamable HTTP, with retries and 429/Retry-After handling.
Who it is for. For YouGile teams who want not a thin wrapper but full API coverage with validation, tests and CI.
Good fit when
- You need access to every YouGile entity, including departments, stickers and webhooks
- You want ready scenarios like board triage or a stand-up report
- You need HTTP transport for remote deployment, not just stdio
Not a fit when
- You only need a narrow set of a couple of tools: 44 tools may be overkill
- You're not ready to give an agent write access to every company resource: the server has no per-level permission split
Example request
Triage the "Development" board and show tasks with no assignee or deadlineLimitations
You need a YouGile API key (Settings → API, or POST /auth/keys). Deletion is soft, via update; there's no separate hard-delete method, but update can still archive or hide an object. The key grants company-wide access; the server does not scope it by project or role.
How to disable. Remove the yougile entry from claude_desktop_config.json or .cursor/mcp.json, or revoke the API key in YouGile settings.
MCP
- Transport
- stdio, http
- Authentication
- API key
| Environment variables | |
|---|---|
| YOUGILE_API_KEY required, secret | YouGile API bearer token. |
| YOUGILE_BASE_URL | API base URL, defaults to https://yougile.com/api-v2. |
Security check
- Full CRUD over every company resource: projects, boards, tasks, users, departments and webhooks
- The API key grants access to the whole company; the server does not scope permissions by role or project
README in short
The bilingual README gives a comparison table against a typical wrapper, a table of 44 tools by resource, a description of resources and prompts, an npx quick start for Claude Desktop and Cursor, an environment variable table, and a source architecture diagram.
FAQ
How is this better than a typical YouGile API wrapper?
The README compares itself: full coverage of all resources, tools plus resources plus prompts, Zod validation on every tool, retries, and tests with CI, not just stdio.
Can it run as a remote server?
Yes, there's a Streamable HTTP mode: YOUGILE_MCP_TRANSPORT=http, endpoint POST /mcp.
Related
Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent
Yandex Kit skills for store management
kit-skills
Yandex's official skill set: catalog, prices, stock, orders, storefront and a weekly checkup for a Yandex Kit store, through Claude Code or Codex
YouGile MCP by Indalo
YouGile MCP
Full 65-operation YouGile API coverage with configurable permissions, write confirmation and a shared company rate limit
Bitrix24 portal MCP server
MCP-сервер портала Битрикс24
Bitrix24's official per-portal MCP: an external agent uses OAuth or a token to read and change tasks, deals, meetings and mail