Bring Photo Editing
to CrewAI
Learn how to connect autoRetouch to CrewAI 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 CrewAI?
When paired with CrewAI, autoRetouch becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call autoRetouch tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
autoRetouch in CrewAI
autoRetouch and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect autoRetouch to CrewAI 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 CrewAI
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 CrewAI 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 CrewAI
Every tool call from CrewAI 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 CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.