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.

Make (Workflow Automation) MCP Server for Claude Desktop 7 tools — connect in under 2 minutes

Name: Make (Workflow Automation)
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 7 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Make (Workflow Automation) and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "make-workflow-automation": {
      // Your Vinkius token — get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About 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.

Claude Desktop is the definitive way to connect Make (Workflow Automation) to your AI workflow. Add the Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 7 tools in the chat interface — ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

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

The Make (Workflow Automation) MCP Server exposes 7 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Make (Workflow Automation) to Claude Desktop via MCP

Follow these steps to integrate the Make (Workflow Automation) MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using Make (Workflow Automation)

Look for the 🔌 icon in the chat — your 7 tools are now available

Why Use Claude Desktop with the Make (Workflow Automation) MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Make (Workflow Automation) through the Model Context Protocol.

Claude Desktop is the reference MCP client — it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage — your tokens never leave your machine, and connections go directly to the Vinkius Edge network

Make (Workflow Automation) + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Make (Workflow Automation) MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies — all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Make (Workflow Automation) MCP Tools for Claude Desktop (7)

These 7 tools become available when you connect Make (Workflow Automation) to Claude Desktop via MCP:

get_scenario

Get Make scenario details

list_connections

List Make connections linked to an organization

list_data_stores

List Make data stores

list_organizations

List Make organizations for the current authenticated user

list_scenario_logs

Helps debug automation errors. Get execution logs of a Make scenario

list_scenarios

Check the list of organizations if org_id is unknown. List Make scenarios

list_teams

Needs org_id. List Make teams inside an organization

Example Prompts for Make (Workflow Automation) in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Make (Workflow Automation) immediately.

"List all organizations in my Make account"

"Show me the execution logs for scenario ID 'scen-98765'"

"List all active connections in organization '12345'"

Troubleshooting Make (Workflow Automation) MCP Server with Claude Desktop

Common issues when connecting Make (Workflow Automation) to Claude Desktop through the Vinkius, and how to resolve them.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting — wait a few seconds.

Make (Workflow Automation) + Claude Desktop FAQ

Common questions about integrating Make (Workflow Automation) MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully — if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL — Claude auto-negotiates the transport protocol.