YouGile MCP by Indalo

YouGile MCP

Full 65-operation YouGile API coverage with configurable permissions, write confirmation and a shared company rate limit

MCP serverEditors’ pickRussian stack

indalo-tech/yougile-mcpAuthor:Indalo

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/indalo-tech-yougile-mcp

Detects 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 -- uvx yougile-mcp

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "yougile": {
      "command": "uvx",
      "args": [
        "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": "uvx",
      "args": [
        "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":"uvx","args":["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": "uvx",
      "args": [
        "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>' -- uvx yougile-mcp

Or add to the file ~/.codex/config.toml, for all projects

[mcp_servers.yougile]
command = "uvx"
args = ["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.

Run in a terminal

gemini mcp add -s user -e 'YOUGILE_API_KEY=<your YOUGILE_API_KEY>' yougile uvx yougile-mcp

Or add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "yougile": {
      "command": "uvx",
      "args": [
        "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": "uvx",
      "args": [
        "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": "uvx",
      "args": [
        "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": "uvx",
      "args": [
        "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": [
        "uvx",
        "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": "uvx",
      "args": [
        "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": "uvx",
      "args": [
        "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.

You will need: uv

Checked against the repository on Sep 25, 2026, commit bbeaf10.

Text for your agent

Get a key with uvx yougile-mcp setup, add the server with claude mcp add yougile --scope user -e YOUGILE_API_KEY=key -- uvx yougile-mcp, and optionally restrict rights via a .yougile.json file with role: reader or member.

Other ways from the author

uvx yougile-mcp setup

The README wizard: asks for a YouGile login and password only to issue the key, storing nothing but the key itself.

This is third-party code. Review the repository files before installing.

What it does

The server's operation catalog is built from YouGile's official OpenAPI spec, and CI tests refuse to release a version where a new API operation is left without a tool. Task tools (yougile_overview, yougile_find_tasks, yougile_task, yougile_create_task, yougile_update_task, yougile_move_task, yougile_log_time, yougile_task_chat, yougile_use_board) take task names and numbers instead of UUIDs. Domain tools cover the whole API across ten groups: tasks, chats, boards, columns, projects, users, stickers, company, files, CRM. Three ready MCP prompts (standup, hours_report, triage) build reports in one command. Permissions are configured via a .yougile.json file: a reader/member/admin role, a list of allowed projects, masked operation denials, and mandatory write confirmation for sensitive projects. The 50-requests-per-minute company-wide limit is enforced by one shared counter across every session running on the machine.

Who it is for. For teams that want not just a YouGile API wrapper but governed access with roles, confirmations and a guarantee of full coverage.

Good fit when

You need to restrict an agent to a read-only role or specific projects via config
You need writes to sensitive projects to require human confirmation
You want ready scenarios: stand-up, hours report, queue triage

Not a fit when

You want the simplest possible server with a couple of tools, not 65 operations with permission configuration
Your client doesn't support MCP elicitation: without it, confirmations and disambiguation fall back to plain error text

Example request

Build an hours report for this week on the "Development" project and show any overruns

Limitations

By default the admin role grants full access, including projects, employees and webhooks; it must be explicitly restricted in .yougile.json. YouGile does not expose Workflow column chains via the API, so they have to be written into the config by hand once. The check command spends 5 requests from the limit. Permission settings only narrow what the key is already allowed in YouGile itself, they don't replace its rights.

How to disable. Run claude mcp remove yougile, or remove the yougile entry from your client config, and delete any .yougile.json files if needed.

MCP

Transport: stdio, http
Authentication: API key

Environment variables
Environment variables
YOUGILE_API_KEY required, secret	YouGile API key.
YOUGILE_BASE_URL	YouGile address, defaults to https://ru.yougile.com; your own for a box install.
YOUGILE_RATE_LIMIT	Requests per minute per key, defaults to 45.

Security check

The default admin role grants full access to the entire API, including employees, projects and webhooks
Permissions only narrow what the key already allows in YouGile, they don't replace the service's own protections

README in short

The bilingual README details the task and domain tools, three ready prompt scenarios, the full .yougile.json settings file format with an example, the confirmation mechanism with and without MCP elicitation, environment variables, and a "how it works" section on checking the operation catalog against the spec in CI.

FAQ

Can I give an agent read-only access?

Yes, set role: reader in .yougile.json, and writes are then denied regardless of the key's own permissions.

What if the client doesn't support confirmations (elicitation)?

The tool returns confirmation_required with the text of the change; the model must show it to the user and repeat the call with confirm=true only after explicit consent.

Salesforce DX MCP Server

Official

Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent

MCP serverHigh risk483

Yandex Kit skills for store management

kit-skills

Official

Yandex's official skill set: catalog, prices, stock, orders, storefront and a weekly checkup for a Yandex Kit store, through Claude Code or Codex

PluginHigh riskRussian stackNo VPN needed28

Bitrix24 portal MCP server

MCP-сервер портала Битрикс24

Official

Bitrix24's official per-portal MCP: an external agent uses OAuth or a token to read and change tasks, deals, meetings and mail

MCP serverHigh riskRussian stackNo VPN needed

WeChat Intelligence Hub

A local-first set of Codex skills and a read-only CLI that turns your own WeChat history into search, digests, follow-ups and opportunity tracking

SkillHigh riskNo VPN needed2.6K

Install

What it does

Good fit when

Not a fit when

Example request

Limitations

MCP

Security check

README in short

FAQ

Related

Salesforce DX MCP Server

Yandex Kit skills for store management

Bitrix24 portal MCP server

WeChat Intelligence Hub