Connect your agent
Connect an agent to inspect the same projects you see in the studio. For your first walkthrough, choose a key that can only read.
Create a key in the studio
Section titled “Create a key in the studio”- Sign in to the studio.
- Open ⋮ → API → Keys and setup → Create key. In Russian: ⋮ → API → Ключи и подключение → Создать ключ.
- Give the key a recognizable name and choose Look only (Только смотреть).
- Copy the key when it appears. It is shown once; a lost key must be replaced with a new one.
This permission exposes reading tools. It does not let the agent change projects or start paid generations. The studio’s key screen also provides the client-specific setup below with your connection details.
Configure your client
Section titled “Configure your client”Vini uses Streamable HTTP at https://vinistudio.app/mcp, with a Bearer key in the Authorization header. Replace placeholders with your own key only in your local client setup.
Claude Code
Section titled “Claude Code”Run this command in your terminal, replacing vini_sk_YOUR_KEY:
claude mcp add --transport http vini https://vinistudio.app/mcp \ --header "Authorization: Bearer vini_sk_YOUR_KEY"Cursor
Section titled “Cursor”Set VINI_API_KEY in the environment used to launch Cursor. Add this entry to ~/.cursor/mcp.json, preserving any other servers you already have:
{ "mcpServers": { "vini": { "url": "https://vinistudio.app/mcp", "headers": { "Authorization": "Bearer ${env:VINI_API_KEY}" } } }}VS Code
Section titled “VS Code”Add this configuration to .vscode/mcp.json. VS Code asks for the key through a hidden input:
{ "servers": { "vini": { "type": "http", "url": "https://vinistudio.app/mcp", "headers": { "Authorization": "Bearer ${input:vini-key}" } } }, "inputs": [ { "id": "vini-key", "type": "promptString", "password": true, "description": "Vini Studio key" } ]}Set VINI_API_KEY in the environment used to launch Codex. Add this server to ~/.codex/config.toml:
[mcp_servers.vini]url = "https://vinistudio.app/mcp"bearer_token_env_var = "VINI_API_KEY"bearer_token_env_var contains the variable’s name, not the key itself.
Check the connection
Section titled “Check the connection”Open a conversation with the connected agent and follow Read your first project and result. Ask the agent to use Vini’s describe_studio tool; an explanation of what MCP is does not verify the connection. Continue through project selection to opening an existing image when the account has one.
If authentication fails, check the key and its environment variable in the client that is actually running. Revoked keys stop working on subsequent requests. You can replace or revoke keys in the same studio screen.
Last checked: 14 October 2026, against the setup supplied by Vini’s key screen. These are the studio’s supported setup formats; the walkthrough is tested through an isolated MCP connection, not by launching every client version. Vini’s current setup uses Bearer keys; an OAuth connection for ChatGPT or Claude.ai is not provided here.
