GigaChat Image MCP: Kandinsky images from Claude with no VPN
GigaChat-image-MCP
Kandinsky images in Claude Code and Desktop through the GigaChat API: background jobs, a call log and confirmation before spending the limit
- 0 ★ on the repository
- Last commit
Extended access
Why this level
- Every generation spends the GigaChat limit and an agent loop without confirmations burns it fast
- Prompts go to an external Sber service and the key sits in the `key.env` file
Install
- Works in
- Services
Manual install
claude mcp add gigachat-image --scope user -e GIGACHAT_KEY_FILE=C:/path/to/gigachat-image-mcp/key.env -e IMAGE_OUTPUT_DIR=C:/path/to/images -e NODE_EXTRA_CA_CERTS=C:/path/to/gigachat-image-mcp/certs/russian_trusted_ca.pem -- node C:/path/to/gigachat-image-mcp/index.jsClone the repository and run `npm install` first; replace the paths with your own and put the key in `key.env`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Every generation spends the GigaChat limit and an agent loop without confirmations burns it fast
- Prompts go to an external Sber service and the key sits in the `key.env` file
This is third-party code. Review the repository files before installing.
What it does
A Node.js MCP server for Claude Code and Claude Desktop draws images from text through the GigaChat API with the built-in Kandinsky model. Two tools: `generate_image` creates an image, saves a JPG to the `IMAGE_OUTPUT_DIR` folder and returns the file path, and `check_image` shows a job status by `job_id` or the list of recent jobs and does not contact Sber. If drawing takes longer than `GIGACHAT_WAIT_MS`, the server returns a `job_id` and generation continues in the background. In the `generate_image` description Claude must ask permission before every call, and all calls are written to `gigachat-image.log`. The key is read from the `GIGACHAT_KEY_FILE` file, and the Russian Ministry of Digital Development root certificate lives in `certs/` and is connected through `NODE_EXTRA_CA_CERTS`.
Who it is for. Claude users in Russia who need illustrations for presentations and documents without foreign cards and a VPN.
Good fit when
- Claude is preparing a presentation and generated pictures have to go into the slides
- An image takes long to draw and the job should be tracked by `job_id` rather than waited for in chat
- Registration and payment should go through Sber ID on the free tier for individuals
- Every generation call should pass through user confirmation
Not a fit when
- You need video, editing of existing pictures or inpainting: the server only creates new images
- You need a one-command npm install: the server installs by cloning the repository and `npm install`
- The GigaChat limit is exhausted: each generation spends it, while `check_image` charges nothing
Example request
Draw a watercolor illustration "autumn park" for a presentation cover and insert the JPG path into the documentMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
GIGACHAT_KEY_FILErequired- Path to the `key.env` file with the GigaChat Authorization Key
IMAGE_OUTPUT_DIR- Folder for saved JPG files
NODE_EXTRA_CA_CERTSrequired- Path to the Russian trusted CA certificate `russian_trusted_ca.pem`
GIGACHAT_WAIT_MS- How long to wait for generation before returning a `job_id`
Limitations
Node.js 20 or newer, a GigaChat API authorization key (shown once) and the Russian Ministry of Digital Development root certificate from the `certs/` folder are required; the intermediate certificate is valid until March 6, 2027 and then has to be replaced with files from Gosuslugi. Generation spends the GigaChat limit, and on the free personal tier the limits are set by Sber. Call confirmation relies on the tool description and on the `permissions.ask` rule in Claude Code settings. The repository is small: zero stars, last commit in November 2026, no license.
How to disable. Remove the server with `claude mcp remove gigachat-image`, erase `key.env` and revoke the key in the Sber developer console.
FAQ
Is a VPN needed?
No: per the README registration goes through Sber ID, there is a free mode for individuals and no foreign cards are required.
Why is a certificate needed?
Sber servers use a certificate from a Russian certificate authority that Node.js does not trust by default; the file is in `certs/` and is connected through `NODE_EXTRA_CA_CERTS`.
What if the image takes long to draw?
The server returns a `job_id`, generation continues in the background and `check_image` shows the status.
How do I make Claude ask permission?
Add a `permissions.ask` rule for `mcp__gigachat-image__generate_image` to `~/.claude/settings.json`.
Where are the finished images?
In the `IMAGE_OUTPUT_DIR` folder as JPG; the server returns the file path in the response.
Discussion
No questions or reviews yet.
Related
All GigaChat toolsGigaChat image generation MCP
mcp-server-gigachat-image-generation
MCP server packaged as a Docker image for generating images with GigaChat, configured with GIGACHAT_CREDENTIALS
An MCP server for image generation through Sber's official Kandinsky API, with style choice and negative prompts
MCP server that checks text for signs of AI generation through the GigaChat API
An unofficial Chrome extension adds an MCP button to the giga.chat chat: servers by URL, OAuth 2.1, local programs and confirmation of every call
MCP server for the GigaChat API
GigaChat API
A small Python MCP server for Sber's GigaChat API: authorizes with a Basic key and calls the models directly from an agent, tested on OpenCode under Windows
An ai-forever proxy that serves GigaChat through OpenAI, Anthropic and Gemini APIs so Claude Code, Codex and Gemini CLI can run on it
README in short
The README briefly explains the purpose, describes the two tools in a table, lists requirements, steps to get a GigaChat key, handling the Ministry of Digital Development certificate and connection to Claude Code and Claude Desktop with a call confirmation rule.