Back to Directory/Automation & Workflow

Make

Build, run and debug Make automation scenarios.

Automation & WorkflowJavaScriptv0.2.0

Make Skills for AI Coding Agents

Give your AI coding agent deep Make expertise — for building, explaining, running and debugging Make scenarios through Make's scenario-management MCP server. Works with any agent that reads skill folders and speaks MCP — Claude Code, Codex, Cursor, GitHub Copilot, Windsurf, Cline, and others.

Skills

SkillWhat it does
make-scenario-referenceThe conventions every tool shares — scopes, the data/remark contract, structure vs configuration, the one-save write model, and what the surface refuses to author — for when a tool answers 403 or refuses something
make-scenario-exploreOrienting in an account — organizations, teams, listing scenarios, explaining what one does, connection health, account-wide checks
make-scenario-buildingCreating and editing scenarios — app and module discovery, connections, resolving account-dependent values, flow control, error handling, subscenarios, AI agents; with references and complete examples
make-scenario-operationsRunning, activating and deactivating, reviewing and debugging executions, investigating a webhook

Prerequisites

Installation

Two pieces, both needed: the skills (the expertise) and the MCP server (the tools the skills drive).

Option A: Plugin (recommended)

Claude Code

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

Cursor — Team Marketplace: import integromat/make-skills and install make. The plugin registers the MCP server (/cursor).

Codex

codex plugin marketplace add integromat/make-skills

Then open the plugin directory, select the Make marketplace, and install make. If the MCP server is not registered automatically, add it manually:

codex mcp add make --url https://mcp.make.com/openai
codex mcp login make

Option B: Download the skills

Upload the zips to your agent (Claude Cowork, Claude Chat, and similar) or unzip them into its skills directory:

SkillDownload
Bundle of all the skillsDownload
Scenario ReferenceDownload
Scenario ExploreDownload
Scenario BuildingDownload
Scenario OperationsDownload

Skills directories, for agents that read skills from disk:

AgentSkills directory
ChatGPT / Codex.codex/skills
Claude Code.claude/skills/
Cursor.cursor/skills/
Windsurf.windsurf/skills/
Cline.cline/skills/
Generic.agents/skills/

Add the MCP server manually

Skip this if a plugin registered it. Each platform has its own endpoint, over HTTP:

PlatformMCP URL
Claude Codehttps://mcp.make.com/claude
Cursorhttps://mcp.make.com/cursor
OpenAI Codexhttps://mcp.make.com/openai
claude mcp add --transport http make https://mcp.make.com/claude
claude mcp list

For any other agent, add the matching URL to its JSON MCP config.

On first use, authenticate through Make's OAuth consent screen. The server asks for one bundle of permissions and works only when every one of them is granted — if a tool answers with a permission error, reconnect and grant everything it asks for.

Troubleshooting

IssueSolution
MCP server not connectingCheck network connectivity to Make servers
Permission denied / 403Reconnect the Make MCP server and grant every requested permission
A tool refuses to create somethingRead the refusal — the surface deliberately cannot author data stores, custom functions or data structures; create those in the Make editor

Contributing

Open pull requests against main — that's the trunk. Use squash merges and Conventional Commit PR titles (feat:, fix:, docs:, …), since release-please relies on them. A separate latest branch is fast-forwarded to each released tag. The Claude Code marketplace entry uses a local ./plugins/make-skills-claude source, so installs track the branch the marketplace is added from. Codex and npx skills add still resolve main HEAD directly. For Cursor Team Marketplace, import this repo and track branch main (branch is not set in .cursor-plugin/marketplace.json).

License

MIT

Setup from the maintainer

This listing does not have a supported local package template. Use the maintainer’s documentation for its hosted endpoint, authentication, and client-specific setup. No install command has been inferred.

Learn More