Unofficial MCP server for Make.com — build, validate & deploy automation scenarios via AI (community project, not affiliated with Make.com)
Most cloud and infrastructure work still happens through a UI a human drives. Make MCP server moves it into the conversation instead. Unofficial MCP server for Make.com — build, validate & deploy automation scenarios via AI (community project, not affiliated with Make.com).
A Model Context Protocol (MCP) server that gives AI assistants like Claude, GitHub Copilot, and Cursor full access to Make.com module documentation, scenario validation, and one-click deployment. Search 200+ automation modules across 40+ apps, build blueprints with auto-healing, and deploy directly to Make.com — all from your AI chat.
The server publishes 8 tools. What each one is for:
tools_documentation — START HERE — Returns comprehensive documentation for all tools, prompts, and resourcessearch_modules — Full-text search across 200+ Make.com modulesget_module — Get detailed module info with parameters and docscheck_account_compatibility — Check if modules are available in your current Make account/region (with suggestions)validate_scenario — Validate a scenario blueprint before deploymentcreate_scenario — Deploy a scenario to Make.com via APIsearch_templates — Search reusable scenario templateslist_apps — List all apps with module countsConfiguration is passed through the environment: LOG_LEVEL, MAKE_API_KEY, MAKE_TEAM_ID, MAKE_API_URL, DATABASE_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
make-mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Make's toolset — tools_documentation, search_modules, get_module and 5 more — is a fair guide to whether it matches your workflow. It is maintained by danielshashko; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| tools_documentation | **START HERE** — Returns comprehensive documentation for all tools, prompts, and resources |
| search_modules | Full-text search across 200+ Make.com modules |
| get_module | Get detailed module info with parameters and docs |
| check_account_compatibility | Check if modules are available in your current Make account/region (with suggestions) |
| validate_scenario | Validate a scenario blueprint before deployment |
| create_scenario | Deploy a scenario to Make.com via API |
| search_templates | Search reusable scenario templates |
| list_apps | List all apps with module counts |
**Claude Desktop config:**
```json
{
"mcpServers": {
"make-mcp-server": {
"command": "node",
"args": ["/absolute/path/to/make-mcp/dist/mcp/server.js"],
"env": {
"LOG_LEVEL": "error",
"MAKE_API_KEY": "your_api_key_here",
"MAKE_TEAM_ID": "your_team_id"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| LOG_LEVEL | Configuration value read at startup. | Optional |
| MAKE_API_KEY | Credential the server authenticates with. | Yes |
| MAKE_TEAM_ID | Configuration value read at startup. | Optional |
| MAKE_API_URL | Endpoint or connection string the server talks to. | Yes |
| DATABASE_PATH | Filesystem location the server is allowed to use. | Optional |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.