Maximum size in bytes for attachment content returned inline.
Applies only to get_content inline responses; save_path uses streaming and is not limited by this setting.
YANDEX_MCP_ATTACH_DIR (optional)
Comma-separated list of absolute directories allowed for saving attachments.
Fully replaces the default directory rules. When set, only the provided directories (and their subdirectories) are allowed.
Default rule: save_path must be inside the system temporary directory (os.TempDir(), for example /tmp), or inside the user home directory. In the home directory, save_path must not point to the home root and must not be within a hidden top-level home subdirectory (for example, ~/.ssh).
Authentication
The project obtains IAM tokens through Yandex Cloud CLI yc. Local mode runs yc on the MCP machine. Remote mode runs it on the workstation.
In local mode, the server obtains IAM tokens by running:
yc iam create-token when YANDEX_CLI_PROFILE is empty.
yc iam create-token --profile <YANDEX_CLI_PROFILE> when YANDEX_CLI_PROFILE is set.
That means:
You must have the Yandex Cloud CLI (yc) installed and available in PATH.
You must have an initialized/authenticated yc profile (typically via yc init).
Set YANDEX_CLI_PROFILE when the server must use a specific yc profile instead of the active profile.
Notes:
Yandex IAM tokens are valid for no more than 12 hours, so long-running use requires periodic refresh.
The server refreshes the token periodically based on YANDEX_IAM_TOKEN_REFRESH_PERIOD (by default every 10 hours; you can set it to 12 to refresh roughly every 12 hours).
When the refresh happens, the server calls yc iam create-token again. If your yc session/profile requires interactive authentication, yc may open your default browser and ask you to log in.
MCP runs on the Linux server; yc and browser login run on your workstation. Install yandex-mcp on both machines and prepare a workstation yc profile. Server-side yc is not needed. Use only trusted machines and users.
Server MCP client
Add this entry to the MCP client running on the server:
Replace the executable path, work with your workstation profile, and the organization ID.
Workstation setup
Install native yc and OpenSSH, with yc available through PATH. Verify the server's SSH host key and configure SSH-key access without password prompts. The server must permit loopback-only reverse forwarding.
From the extracted release archive or repository, run in your graphical desktop session:
export YANDEX_MCP_BINARY=/absolute/workstation/path/to/yandex-mcp
export [email protected]
sh scripts/remote-auth/macos/install.sh
On a systemd-integrated Linux desktop, replace macos with linux. On Windows, use PowerShell:
Replace the workstation executable path and SSH destination. The installer configures one auth-agent startup entry. Auth-agent starts and reconnects SSH. The executable path overrides are optional when yandex-mcp and yc are in PATH; use YANDEX_MCP_AUTH_AGENT_YC_PATH to override the yc path.
Use the same YANDEX_MCP_AUTH_AGENT_PORT on both machines, default 18765.
Restart the MCP connection and call a Wiki or Tracker tool. Complete login in the workstation browser when prompted. Keep the workstation awake and connected when a new token is needed. The tool timeout defaults to 300 seconds; change YANDEX_MCP_TOOL_TIMEOUT in the server configuration if needed.
Client configuration examples
Claude Code
claude mcp add -s user -e YANDEX_CLOUD_ORG_ID={yandex organization id} -e YANDEX_CLI_PROFILE={yc profile name} --transport stdio yandex /path/to/yandex-mcp
When you need to work with two organizations, configure two independent MCP server entries. Each entry should use its own YANDEX_CLOUD_ORG_ID and YANDEX_CLI_PROFILE.