Make Mcp
Wire your coding agent into Make.com so it can validate blueprint JSON and deploy automation scenarios without clicking through the Make UI.
Overview
make-mcp is a MCP server for the Build phase that lets AI agents build, validate, and deploy Make.com automation scenarios over the Make API.
What is this MCP server?
- stdio npm package make-mcp-server v1.3.3 with optional MAKE_API_KEY, MAKE_TEAM_ID, and EU/default MAKE_API_URL
- Build, validate, and deploy Make.com scenarios from natural-language requests in Claude Code or Cursor
- Unofficial Make.com API client surfaced as MCP tools for AI-driven scenario authoring
- Optional credentials so read/validate paths can work before you commit an API key for create_scenario
- LOG_LEVEL control (error, info, debug) for troubleshooting agent-driven deploys
- Server version 1.3.3 on npm package make-mcp-server
- Optional env vars: MAKE_API_KEY, MAKE_TEAM_ID, MAKE_API_URL (default eu1.make.com/api/v2), LOG_LEVEL
Community signal: 5 GitHub stars.
What problem does it solve?
Hand-building and deploying Make scenarios module-by-module breaks flow when you are already living inside Claude Code or Cursor.
Who is it for?
Solo builders who run Make.com for no-code glue and want the same agent that writes code to own scenario changes.
Skip if: Teams that forbid unofficial API clients, need enterprise Make governance only in the native UI, or do not use Make at all.
What do I get? / Deliverables
Your agent can propose, validate, and optionally deploy Make scenarios using your team credentials so integrations ship faster with fewer UI context switches.
- Validated Make scenario definitions ready to import or deploy
- Deployed scenarios in your Make team when credentials are configured
- Agent-callable tools for iterative scenario edits
Recommended MCP Servers
Journey fit
Make scenarios are product integrations and backend workflows solo builders add while assembling their stack. This MCP is a direct bridge to a third-party automation platform, which is the integrations shelf on the build journey.
How it compares
Make.com API MCP integration, not a local agent skill that replaces Make modules.
Common Questions / FAQ
Who is make-mcp for?
Indie and solo builders using Make.com who want Claude Code, Cursor, or similar agents to author and deploy scenarios via MCP.
When should I use make-mcp?
Use it during build and operate when you need to create, validate, or deploy Make automation from the agent instead of the Make visual editor.
How do I add make-mcp to my agent?
Install the npm make-mcp-server package, configure stdio MCP in your client, and set MAKE_API_KEY and MAKE_TEAM_ID when you need create_scenario deploy.