
Make
io.github.integromatv0.2.0Updated Oct 7, 2026
Build, run and debug Make automation scenarios.
Overview
Lets an AI coding agent build, explain, run and debug Make automation scenarios through Make's scenario-management MCP server.
- What it does
- Connects an agent to Make's scenario-management MCP server so it can orient in an account (organizations, teams, scenario lists, connection health), create and edit scenarios with app and module discovery, and run, activate, deactivate, review and debug executions. It is paired with Make skill folders that supply the conventions, references and examples the tools rely on. The surface deliberately cannot author data stores, custom functions or data structures, which must be created in the Make editor.
- When to use it
- Use it when you already work in Make and want an agent to help design, explain, operate or troubleshoot scenarios instead of clicking through the editor. It suits agents that read skill folders and speak MCP, such as Claude Code, Codex, Cursor, GitHub Copilot, Windsurf or Cline.
- Requirements
- A Make account and network access to Make servers. The remote MCP endpoint is added per platform over HTTP (for example /cursor or /openai), and the matching skill folder must be installed for the agent. Authentication happens on first use through Make's OAuth consent screen, and every requested permission must be granted.
Installation
In SourceWeft
- Open Make in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"make": {
"type": "http",
"url": "https://mcp.make.com/v2"
}
}
}README
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
Prerequisites
- A Make account
Installation
Two pieces, both needed: the skills (the expertise) and the MCP server (the tools the skills drive).
Option A: Plugin (recommended)
Claude Code
Cursor — Team Marketplace: import integromat/make-skills and install make. The plugin registers the MCP server (/cursor).
Codex
Then open the plugin directory, select the Make marketplace, and install make. If the MCP server is not registered automatically, add it manually:
Option B: Download the skills
Upload the zips to your agent (Claude Cowork, Claude Chat, and similar) or unzip them into its skills directory:
Skills directories, for agents that read skills from disk:
Add the MCP server manually
Skip this if a plugin registered it. Each platform has its own endpoint, over HTTP:
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
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
Source: README.md at commit 21a94a0
Tools
0Version history
1- v0.2.0LatestOct 7, 2026

