How to Use the Make (Workflow Automation) MCP in Claude Code

Q: What's the command to list all scenarios for a specific org in Make (Workflow Automation) with Claude Code?

First, get your org ID with claude mcp exec make-workflow-automation-mcp listorganizations. Then, run claude mcp exec make-workflow-automation-mcp listscenarios --orgid YOURORGID to get the list.

Q: How do I check for unauthorized connections in Make (Workflow Automation) from the terminal using Claude Code?

Run claude mcp exec make-workflow-automation-mcp listconnections --orgid YOURORGID. Pipe the JSON output to jq to filter and check against an allowlist of approved connection types.

Pipe your Make.com monitoring into any script or CI/CD pipeline with Claude Code and this MCP Server.

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 Claude Code

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Automate Audits with this MCP Server

Use this server in your shell scripts. A simple cron job can call `claude mcp exec make-workflow-automation-mcp list_scenarios` and pipe the output to `jq` to check for scenarios that haven't run recently. You can build a daily health check script that calls `list_scenarios`, loops through them, and uses `list_scenario_logs` to check for new errors. If it finds any, it pipes the results to a Slack notification script. Set it and forget it.

Monitor Scenarios from the Terminal

Forget the web UI. To check on a failing workflow, just run `claude mcp exec make-workflow-automation-mcp list_scenario_logs --scenario_id 12345`. You get the raw log data instantly, right in your terminal. The output is clean JSON, so you can pipe it to anything. Grep for specific error messages, use `jq` to transform the output, or feed it into a monitoring tool like Datadog. It's built for command-line workflows.

Manage Access in Your CI/CD Pipeline

Before a deployment, you can have your GitHub Action run a check. Use `list_connections` to verify that only approved API endpoints are being used. If a rogue connection appears, the build fails. You can also use `list_teams` to ensure the right people have access before deploying changes that depend on a scenario. This lets you bake compliance checks right into your development pipeline.

Setup guide

Set up Make (Workflow Automation) MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see make-workflow-automation-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Make (Workflow Automation) transactions." It will automatically discover and invoke the available Make (Workflow Automation) tools.

Terminal

claude mcp add --transport http make-workflow-automation-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Make (Workflow Automation) MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

{
  "mcpServers": {
    "make-workflow-automation-mcp": {
      "type": "url",
      "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 Claude Code

In your pipeline script, use Claude Code to execute tools from this MCP server. For example, call `list_scenario_logs` and fail the build if any recent errors are found. It's a simple way to gate deployments.

First, get your org ID with `claude mcp exec make-workflow-automation-mcp list_organizations`. Then, run `claude mcp exec make-workflow-automation-mcp list_scenarios --org_id YOUR_ORG_ID` to get the list.

Run `claude mcp exec make-workflow-automation-mcp list_connections --org_id YOUR_ORG_ID`. Pipe the JSON output to `jq` to filter and check against an allowlist of approved connection types.

No. This toolset is for observing your Make environment, not changing it. You can see scenarios with `list_scenarios` and check logs with `list_scenario_logs`, but you can't start, stop, or edit them.

The server only handles metadata about your Make account: scenario configurations, team rosters, connection details, and execution logs. The Vinkius platform ensures each CLI command runs in an isolated, short-lived container, and your token is the only thing connecting you to the service. No data is stored.

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