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 VS Code Copilot 7 tools — connect in under 2 minutes

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

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 7 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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": {
      "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.

GitHub Copilot Agent mode brings Make (Workflow Automation) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 7 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the Make (Workflow Automation) MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Make (Workflow Automation)

Ask Copilot: "Using Make (Workflow Automation), help me...". 7 tools available

Why Use VS Code Copilot with the Make (Workflow Automation) MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Make (Workflow Automation) through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Make (Workflow Automation) + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Make (Workflow Automation) MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Make (Workflow Automation) MCP Tools for VS Code Copilot (7)

These 7 tools become available when you connect Make (Workflow Automation) to VS Code Copilot 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 VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot

Common issues when connecting Make (Workflow Automation) to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Make (Workflow Automation) + VS Code Copilot FAQ

Common questions about integrating Make (Workflow Automation) MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.