Bring Photo Editing
to Cursor
Learn how to connect autoRetouch to Cursor 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 Cursor?
Cursor's Agent mode turns autoRetouch into an in-editor superpower. Ask Cursor to generate code using live data from autoRetouch and it fetches, processes, and writes. all in a single agentic loop. 11 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
autoRetouch in Cursor
autoRetouch and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect autoRetouch to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.