By integromat
Build, deploy, and manage Make.com automation scenarios from Claude Code using reusable API shells, code artifacts, MCP server configuration, and module setup guides
This skill should be used when Claude needs to build or reuse a reusable Make API-call shell by discovering the correct app-specific Make an API Call module, resolving or requesting the right connection, explicitly setting the scenario interface, running the scenario, and using that shell as the retrieval transport for email, CRM, tickets, and similar SaaS systems.
Use this skill when an agent needs to write reusable code, store it under the configured Hermes Code folder, run it directly through local code execution, or host it behind a Make-managed E2B Code Shell scenario. Use for tool-building, generated business automation scripts, and nested flows where hosted code calls Make API shell scenarios for SaaS access without receiving raw OAuth, Make, or E2B secrets.
This skill should be used when the user asks about "Make MCP server", "Make MCP tools", "MCP token", "Make OAuth", "scenario as tool", "MCP scopes", "Make API access", "connect Make to Claude", "scenario not appearing", "MCP timeout", "MCP connection refused", or discusses configuring, troubleshooting, or understanding the Make.com MCP server integration. Provides technical reference for connection methods, scopes, access control, and troubleshooting.
This skill should be used when configuring Make module parameters, assigning connections, mapping data between modules, setting up webhooks or data stores in modules, working with IML expressions, handling keys, or defining data structures for module inputs/outputs. Covers the practical HOW of module configuration — complementary to make-scenario-building which covers WHICH modules to use and WHY.
This skill should be used when designing Make scenarios, choosing which modules to use, composing module flows, setting up routing/branching/filtering/iterations/aggregations, building blueprints, deploying scenarios, handling errors, configuring scheduling and triggers, or discussing scenario architecture. Covers WHICH modules to use and WHY — complementary to make-module-configuring which covers HOW to configure each module.
External network access
Connects to servers outside your machine
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Give your AI coding agent deep Make expertise — for building workflow automation and Make AI Agents. Works with Claude Code and Codex via dedicated plugins, and with Cursor, GitHub Copilot, Windsurf, Cline, and 40+ other agents via the Open Agent Skills protocol.
Recommended: The Claude Code plugin gives the best experience — skills and MCP server load automatically, with no manual setup.
| Skill | What it does |
|---|---|
| make-scenario-building | End-to-end scenario design — app discovery, module selection, blueprint construction, routing, error handling, deployment |
| make-module-configuring | Module configuration workflow — parameter filling, connections, mapping, webhooks, data stores, IML expressions, validation |
| make-mcp-reference | MCP server reference — configuration, OAuth/token auth, scopes, troubleshooting |
| make-api-shell-connection-workflow | Reusable Make API-call shell provisioning — app discovery, connection request/reuse, interface setup, shell execution, SaaS retrieval transport |
claude
/plugin marketplace add integromat/make-skills
/plugin install make-skills@make-marketplace
Skills and MCP server load automatically — nothing to configure manually.
git clone https://github.com/integromat/make-skills.git
claude
/plugin add /path/to/make-skills
Download individual skills as zip files and upload to your project:
| Skill | Download |
|---|---|
| Scenario Building | Download |
| Module Configuring | Download |
| MCP Reference | Download |
| API Shell + Connection Workflow | Download |
Or download the complete bundle with all 4 skills + MCP config.
codex plugin marketplace add integromat/make-skills
Then open the plugin directory, select the Make marketplace, and install make-skills.
If the MCP server is not registered automatically after install, add it manually:
codex mcp add make --url https://mcp.make.com
codex mcp login make
npx skills add integromat/make-skills
Installs all four skills into your agent's skills directory. Works with any agent that supports the Open Agent Skills protocol — Cursor, GitHub Copilot, Windsurf, Cline, and 40+ others. Technical setup required.
Copy the skills/ directory into your agent's skills folder:
| Agent | Skills directory |
|---|---|
| Claude Code | .claude/skills/ |
| Cursor | .cursor/skills/ |
| Windsurf | .windsurf/skills/ |
| Cline | .cline/skills/ |
| Generic | .agents/skills/ |
Add to your agent's MCP configuration:
{
"mcpServers": {
"make": {
"type": "http",
"url": "https://mcp.make.com"
}
}
}
On first use, you'll authenticate through Make's OAuth consent screen.
For granular access control (team/scenario-level filtering):
mcp:use scope plus any additional scopes for resources you want to access (e.g., scenarios:read, scenarios:write, connections:read){
"mcpServers": {
"make": {
"type": "http",
"url": "https://<MAKE_ZONE>/mcp/u/<MCP_TOKEN>"
}
}
}
Replace <MAKE_ZONE> with your zone (e.g., eu1.make.com) and <MCP_TOKEN> with your token.
Restrict access via URL query parameters:
?organizationId=<id>?teamId=<id>?scenarioId=<id> or ?scenarioId[]=<id1>&scenarioId[]=<id2>| Issue | Solution |
|---|---|
| MCP server not connecting | Check network connectivity to Make servers |
| No scenarios available | Set scenarios to active + on-demand scheduling |
| Permission denied | Check token scopes (mcp:use) |
| Timeout errors | Use SSE transport, reduce scenario complexity |
For Claude Code: run claude --debug for detailed MCP connection logs.
MIT
npx claudepluginhub integromat/make-skills --plugin make-skillsCreate Make.com (Integromat) scenarios with AI assistance - visual automation design
Editorial "Automation Builder" bundle for Claude Code from Antigravity Awesome Skills.
Connect 9,000+ apps to your AI workflow. Discover, enable, and execute Zapier actions directly from your client.
Generate n8n automation workflows from natural language descriptions
Use this agent when you need to design, build, or validate n8n automation workflows. This agent specializes in creating efficient n8n workflows using proper validation techniques and MCP tools integration.\n\nExamples:\n- <example>\n Context: User wants to create a Slack notification workflow when a new GitHub issue is created.\n user: "I need to create an n8n workflow that sends a Slack message whenever a new GitHub issue is opened"\n assistant: "I'll use the n8n-workflow-builder agent to design and build this GitHub-to-Slack automation workflow with proper validation."\n <commentary>\n The user needs n8n workflow creation, so use the n8n-workflow-builder agent to handle the complete workflow design, validation, and deployment process.\n </commentary>\n</example>\n- <example>\n Context: User has an existing n8n workflow that needs debugging and optimization.\n user: "My n8n workflow keeps failing at the HTTP Request node, can you help me fix it?"\n assistant: "I'll use the n8n-workflow-builder agent to analyze and debug your workflow, focusing on the HTTP Request node configuration."\n <commentary>\n Since this involves n8n workflow troubleshooting and validation, use the n8n-workflow-builder agent to diagnose and fix the issue.\n </commentary>\n</example>\n- <example>\n Context: User wants to understand n8n best practices and available nodes for a specific use case.\n user: "What are the best n8n nodes for processing CSV data and sending email reports?"\n assistant: "I'll use the n8n-workflow-builder agent to explore the available nodes and recommend the best approach for CSV processing and email automation."\n <commentary>\n This requires n8n expertise and node discovery, so use the n8n-workflow-builder agent to provide comprehensive guidance.\n </commentary>\n</example>
Genesis (Forerunner) - AI-Powered Executive Director Automation Platform. Analyze organizational responsibilities, score automation potential with 6-factor algorithm, generate LangGraph workflows, and deploy 11 specialized agents for trade associations and nonprofits.