A
licenseA
qualityA
maintenanceConnects Claude to Make.com to manage scenarios: list, run, activate/deactivate, and monitor executions.
26
1
MIT
Make.com MCP Server
Related Servers
Alternatives to Make.com MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn integration server that allows Claude Desktop to communicate with Make (formerly Integromat) automation platform through the Model Context Protocol, enabling scenario management and execution via natural language.101 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to trigger and interact with Make automation workflows by exposing on-demand scenarios as callable tools. Allows AI systems to invoke Make scenarios with parameters and receive structured JSON responses.120 npmMIT
- AlicenseDqualityFmaintenanceTransform your Make scenarios into callable tools for AI assistants. Leverage your existing automation workflows while enabling AI systems to trigger and interact with them seamlessly.6120 npm173MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search 200+ Make.com modules, validate and auto-heal blueprints, and deploy automation scenarios directly to Make.com via API.101 npm8MIT
- AlicenseNot gradedqualityDmaintenanceEnables automation of Google Workspace tasks, including reading/writing sheets, generating Apps Script code, and creating webhook senders, with AI assistance via Claude.1,546 npmMIT
TDQS
B3/5.0
Scored across 3 tools
Disambiguation5/5
Each tool has a clearly distinct purpose with no overlap: get_scenario_status retrieves status, test_webhook_connection checks connectivity, and trigger_make_scenario initiates execution. The descriptions reinforce these distinct functions, making misselection unlikely.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with snake_case: get_scenario_status, test_webhook_connection, and trigger_make_scenario. The naming is predictable and readable throughout the set.
Tool Count3/5
With only 3 tools, the set feels thin for a Make.com integration server, which typically involves more operations like managing scenarios, webhooks, or data. While the tools cover core actions, the count is borderline minimal for the apparent scope.
Completeness2/5
There are significant gaps in the tool surface for a Make.com server. Missing operations include creating, updating, or deleting scenarios, listing scenarios, managing webhooks beyond testing, and handling data flows. This will likely cause agent failures in broader workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues