How to Use the Make (Workflow Automation) MCP in CrewAI

Q: Can agents in CrewAI share state using Make (Workflow Automation) data stores?

Yes. Agents can read and update your data stores using listdatastores. This acts as a shared memory for your crew to coordinate their work.

Q: How does CrewAI handle tool permissions for Make (Workflow Automation)?

Use the toolfilter in your MCP configuration to limit which agents can access sensitive functions. This keeps your write-access tools restricted to specific agents.

Deploy autonomous agent crews to monitor and manage your Make (Workflow Automation) infrastructure.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Make (Workflow Automation) MCP to CrewAI

Create your Vinkius account to connect Make (Workflow Automation) to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Make (Workflow Automation) with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Specialized agents for scenario auditing

Assign a dedicated auditor agent to scan your workspace. Using `list_scenarios`, the agent keeps a running inventory of all your active workflows and their status. It removes the manual effort of checking if your automations are still healthy. The agent reports back only when it finds something that requires your attention.

Autonomous error resolution crews

Create a team where one agent monitors logs and another executes fixes. By querying `list_scenario_logs`, the monitor agent identifies bottlenecks, while the moderator agent acts to clear them. This creates a closed-loop system for your operations. You spend your time building new things instead of babysitting existing ones.

Multi-agent workspace management

Manage your entire organization structure with ease. Agents use `list_teams` and `list_organizations` to map out your architecture and assign tasks to the correct segments. It allows your crew to operate across complex setups. Each agent knows exactly which part of the organization it is responsible for.

Setup guide

Set up Make (Workflow Automation) MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Make (Workflow Automation) tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Make (Workflow Automation) Analyst",
    goal="Access and analyze Make (Workflow Automation) data via MCP.",
    backstory="Expert analyst with direct Make (Workflow Automation) access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Make (Workflow Automation) transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Make (Workflow Automation) Analyst",
        goal="Access and analyze Make (Workflow Automation) data via MCP.",
        backstory="Expert analyst with direct Make (Workflow Automation) access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Make (Workflow Automation) transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Make. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Make (Workflow Automation) now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Make (Workflow Automation) MCP in CrewAI

Pass the server URL directly into your agent's MCP configuration. This allows the agents in your crew to share the tools and collaborate on automation tasks.

Yes. Agents can read and update your data stores using `list_data_stores`. This acts as a shared memory for your crew to coordinate their work.

Use the `tool_filter` in your MCP configuration to limit which agents can access sensitive functions. This keeps your write-access tools restricted to specific agents.

The server supports multiple transport types including stdio and SSE. This makes it perfect for running your crews in CI/CD pipelines or background workers.

The connection is restricted to your specific Vinkius endpoint token. Your logs are only fetched into the agent's memory during the session and are discarded immediately after.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript