Bring Workflow Orchestration
to CrewAI
Create your Vinkius account to connect Make (Workflow Automation) to CrewAI and start using all 7 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Make (Workflow Automation) MCP Server?
Connect your Make account to any AI agent and take full control of your visual workflow automation and scenario management through natural conversation.
What you can do
- Scenario Orchestration — List all managed scenarios and retrieve detailed flow design structures, including module mappings and trigger settings directly from your agent
- Execution Diagnostics — Extract historical scenario logs to identify errors, track data processing volumes, and debug automation failures in real-time
- Infrastructure Audit — Enumerate active organizations, teams, and connections to understand your automation footprint and verify authentication hooks securely
- Data Store Visibility — List and inspect internal Make Data stores (key-value tables) to monitor persistent data used across your automated workflows
- Environment Mapping — Retrieve precise organization and team IDs required for complex downstream API operations and organizational auditing
- Metadata Inspection — Deep-dive into specific scenario configurations to understand the logic and logic loops powering your business processes
How it works
- Subscribe to this server
- Enter your Make API Token and Zone (e.g., eu1, us1)
- Start managing your automation infrastructure from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Automation Engineers — verify scenario designs and audit connection statuses through natural conversation without manual dashboard navigation
- Ops Managers — monitor execution logs and scenario health across multiple teams to ensure business process reliability
- Developers — inspect data store contents and retrieve scenario metadata directly from your workspace for rapid debugging
Built-in capabilities (7)
Get Make scenario details
List Make connections linked to an organization
List Make data stores
List Make organizations for the current authenticated user
Helps debug automation errors. Get execution logs of a Make scenario
Check the list of organizations if org_id is unknown. List Make scenarios
Needs org_id. List Make teams inside an organization
Why CrewAI?
When paired with CrewAI, Make (Workflow Automation) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Make (Workflow Automation) 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
Make (Workflow Automation) in CrewAI
Why run Make (Workflow Automation) with Vinkius?
The Make (Workflow Automation) connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 7 tools are ready to work instantly without any complex setup.
You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.
* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure
Over 4,000 integrations ready for AI agents
Explore a vast library of pre-built integrations, optimized and ready to deploy.
Connect securely in under 30 seconds
Generate tokens to authenticate and link external services in a single step.
Complete visibility into every agent action
Audit live requests, latency, success rates, and active security compliance policies.
Optimize spending and track token ROI
Analyze real-time token consumption and cost metrics detailed by connection.
Explore our live AI Agents Analytics dashboard to see it all working
This dashboard is included when you connect Make (Workflow Automation) using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.
Make (Workflow Automation) and 4,000+ other AI tools. No hosting, no code, ready to use.
Professionals who connect Make (Workflow Automation) to CrewAI through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.
Raw MCP | Vinkius | |
|---|---|---|
| Ready-to-use MCPs | Find and configure each manually | 4,000+ MCPs ready to use |
| Connection Setup | Manual coding & server setup | 1-click instant connection |
| Server Hosting | You host it yourself (needs 24/7 uptime) | 100% hosted & managed by Vinkius |
| Security & Privacy | Stored in plaintext config files | Bank-grade encrypted vault |
| Activity Visibility | Blind execution (no logs or tracking) | Live dashboard with real-time logs |
| Cost Control | Runaway AI token spend risk | Automatic budget limits |
| Revoking Access | Must delete files or code to stop | 1-click disconnect button |
How Vinkius secures
Make (Workflow Automation) for CrewAI
Every request between CrewAI and Make (Workflow Automation) is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.
Frequently asked questions
Can I see the modules and filters used in a Make scenario through my agent?
Yes. Use the get_scenario tool with a specific Scenario ID. Your agent will retrieve the complete design structure, exposing the modules, mapping variables, and any logic filters configured in the flow.
How do I find out why a Make scenario failed recently?
The list_scenario_logs tool allows your agent to extract the execution history for a given scenario. You'll be able to see exactly when the failure occurred and retrieve the error message to assist with debugging.
Can my agent list all active connections in my Make organization?
Absolutely. Use the list_connections tool with your Organization ID. Your agent will report all configured auth hooks, helping you audit which services are currently linked to your Make account.
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.
Explore More MCP Servers
View all →
FinLegal
12 toolsManage litigation funding cases, track claim progress, and coordinate legal finance workflows for law firms and funders.
Wolai
10 toolsAll-in-one information organization and collaboration platform — manage pages, databases, and blocks via AI.
Fera.ai
12 toolsManage reviews and social proof via Fera.ai — list customer feedback, track product ratings, and monitor UGC directly through your AI agent.
Halo Security
11 toolsAutomate attack surface management via Halo Security — monitor assets, scans, and vulnerabilities directly from any AI agent.