Bring Photo Editing
to Claude Desktop
Learn how to connect autoRetouch to Claude Desktop and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the autoRetouch MCP Server?
Connect your autoRetouch account to any AI agent and take full control of your automated image editing and high-fidelity retouching workflows through natural conversation.
What you can do
- Workflow Orchestration — Execute complex high-fidelity AI workflows for background removal, color correction, and shadow generation programmatically
- Bulk Processing Intelligence — Programmatically upload raw images and monitor their processing status in real-time to maintain a perfectly coordinated media pipeline
- Result Discovery — Retrieve high-fidelity result URLs for processed images and access detailed metadata for every individual execution
- Lifecycle Management — Group multiple executions into tracked batches to oversee your organization's image editing volume efficiently
- Financial Visibility — Access your organization's wallet balance and profile metadata directly through your agent for instant operational reporting
How it works
1. Subscribe to this server
2. Retrieve your API Token and Organization ID from your autoRetouch dashboard (API settings)
3. Start localizing and retouching your media assets from Claude, Cursor, or any MCP client
No more manual dragging into web tools for repeatable editing tasks. Your AI acts as your dedicated digital imaging engineer and workflow coordinator.
Who is this for?
- E-commerce Merchants — instantly process high-volume product photos for catalog updates using natural language commands
- Marketing Agencies — automate the removal of backgrounds and color balancing without leaving your creative workspace
- Photographers — orchestrate complex retouching sequences across large batches through simple AI queries
Built-in capabilities (11)
Returns the execution ID. Start an image processing execution
Get details of a specific batch
Get details of a specific execution
Get details of a specific image
Get organization details
Get account wallet balance
Get details of a specific workflow
List all batches
List recent executions
List uploaded images
List all image processing workflows
Why Claude Desktop?
Claude Desktop is the definitive way to connect autoRetouch to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 11 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
autoRetouch in Claude Desktop
autoRetouch and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect autoRetouch to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for autoRetouch in Claude Desktop
The autoRetouch MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 11 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
autoRetouch for Claude Desktop
Every tool call from Claude Desktop to the autoRetouch MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my autoRetouch API credentials?
Log in to your account, navigate to the API section to generate an Access Token (Bearer), and find your Organization ID in the organization settings.
Can I process multiple images at once?
Yes! You can trigger individual executions programmatically and group them into a single batch for high-fidelity tracking.
What happens if a process fails?
The get_execution_status tool will return high-fidelity error metadata to help you diagnose and re-run the task programmatically.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.