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

Q: Does this MCP Server allow Cline to modify my Make connections?

No, it's strictly read-only. Cline can use listconnections to show you what's configured, but it cannot add, delete, or update any of your connections. Your credentials are safe.

Let Cline use this MCP server to manage your Make workflows, audit scenarios, and pull logs directly into VS Code.

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 Cline

Create your Vinkius account to connect Make (Workflow Automation) to Cline 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 Cline

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Build Internal Dashboards with Live Data

Tell Cline to build a monitoring dashboard for your Make account. It can use this MCP server to call `list_scenarios` and `list_scenario_logs`, then write the frontend code to display the status of each workflow. Cline will generate the React or Vue component, fetch the data, and even write tests for it. You go from a prompt to a working dashboard component that shows real-time scenario health without leaving your editor.

Audit Your Make Setup with Cline

Ask Cline to 'generate a security report for Make'. It'll use `list_connections` to find all API keys and `list_teams` to map out user access. It can then format this information into a markdown file for your records. This isn't just about getting data; it's about getting a finished artifact. Cline takes the raw JSON from the API calls and turns it into a human-readable report, saving you the parsing and formatting work.

Debug Workflows Without the UI

When a workflow fails, you don't need to open your browser. Just highlight the scenario name in your notes and ask Cline to 'get the logs for this'. It'll grab the scenario ID with `get_scenario` and then fetch the error details using `list_scenario_logs`. The logs can be dropped in as a comment, a new file, or directly in the chat. Cline can even suggest a fix based on the error message. It’s a much tighter debug loop than context-switching to the Make website.

Setup guide

Set up Make (Workflow Automation) MCP in Cline

Prerequisites

VS Code with Cline extension installed
Active Vinkius subscription with a valid endpoint token

1

Open Cline MCP settings

Click the Cline icon in the VS Code sidebar to open the Cline panel. Then click the MCP Servers icon (server stack) at the top-right corner of the panel.
2

Add a remote server

Click "Remote Servers" at the top, then click "Add Remote MCP". In the Name field, type make-workflow-automation-mcp. In the URL field, paste your Vinkius endpoint: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp. Get your token from cloud.vinkius.com.
3

Enable the server

After saving, the server appears in the Cline MCP panel. Toggle the switch to enable it. The status indicator turns green when the connection is live.
4

Start using tools

Return to the Cline chat and ask: "Check my latest Make (Workflow Automation) refund status." Cline will discover the available tools and request your approval before invoking each one — giving you full control over every action.

Cline MCP Settings

{
  "mcpServers": {
    "make-workflow-automation-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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 Cline

Just ask Cline: "List all Make data stores and save them to a JSON file." It will call `list_organizations` to get the ID, then `list_data_stores`, and write the output to a new file in your workspace.

Absolutely. Tell Cline "Find the error logs for the 'customer sync' scenario." It will find the right scenario and use `list_scenario_logs` to pull the specific error message and execution details right into VS Code.

Yes. You can ask Cline to fetch the details for two different scenarios using `get_scenario` for each. Then, ask it to "diff these two JSON objects" to see the differences in their configuration.

No, it's strictly read-only. Cline can use `list_connections` to show you what's configured, but it cannot add, delete, or update any of your connections. Your credentials are safe.

This server only requests metadata like your organization structure, scenario names, and execution logs from Make. Vinkius processes these requests in ephemeral, zero-trust environments. Your actual business data within Make data stores is not accessed.

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