make-skills

Expert skills for designing, building, and deploying Make.com automation scenarios — for Claude Code, Cursor, GitHub Copilot, and other AI agents.

Skills

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

Prerequisites

• A Make.com account
• Active scenarios with on-demand scheduling (for MCP tool access)

Installation

Any Agent (via Open Agent Skills)

npx skills add integromat/make-skills

Installs all three skills into your agent's skills directory. Works with Claude Code, Cursor, GitHub Copilot, Windsurf, Cline, and 40+ other agents.

Claude Code Plugin (Marketplace)

claude
/plugin marketplace add integromat/make-skills
/plugin install make-skills@make-marketplace

Claude Code Plugin (Manual)

git clone https://github.com/integromat/make-skills.git
claude
/plugin add /path/to/make-skills

Claude Desktop / Claude.ai

Download individual skills as zip files:

Skill	Download
Scenario Building	Download
Module Configuring	Download
MCP Reference	Download

Or download the complete bundle with all 3 skills + MCP config.

Manual Installation (Any Agent)

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/

MCP Server Setup

OAuth (Recommended)

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.

MCP Token

For granular access control (team/scenario-level filtering):

1. Generate a token in Make: Profile → API access → Add token
2. Select the mcp:use scope plus any additional scopes for resources you want to access (e.g., scenarios:read, scenarios:write, connections:read)
3. Configure:

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

Access Control (Token Auth)

Restrict access via URL query parameters:

• Organization: ?organizationId=<id>
• Team: ?teamId=<id>
• Scenario: ?scenarioId=<id> or ?scenarioId[]=<id1>&scenarioId[]=<id2>

Troubleshooting

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.

License

MIT