MCP Make.com Server
Related Servers
Alternatives to MCP Make.com Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceProvides AI assistants with full access to manage n8n workflows, executions, credentials, and pipeline building via the Model Context Protocol.-
- AlicenseNot gradedqualityCmaintenanceProvides full access to amoCRM API v4, enabling AI platforms to search, create, update, and bulk-manage leads, contacts, companies, tasks, notes, and reports, configure pipelines and fields, and call any API method through MCP tools.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding assistants to inspect and operate Make workflows, including scenario deployment and data store management, through natural language.MIT

Strait MCP serverofficial
AlicenseAqualityBmaintenanceEnables AI tools to create, inspect, update, and deactivate deep links, read analytics, usage, and referral data, manage webhook deliveries, check App Links / Universal Links files, and search bundled documentation.31153 npmMIT
Marsell MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables AI clients to read and act on projects, brand and market data, people, analytics, decisions, and token balances, with scoped permissions for content, marketing, sales workflows, image creation, business setup, missions, and browser-based messaging.MIT- AlicenseNot gradedqualityNot gradedmaintenanceEnables comprehensive interaction with the Airtable Web API to manage bases, tables, and records. It supports advanced features like batch record operations, CSV import/export, attachment uploads, and webhook management.-
TDQS
Scored across 21 tools
Each tool targets a distinct resource and action (scenario lifecycle, data stores, teams, orgs, user, connections, hooks). The scenario tools are clearly differentiated by verb: get, list, create, update, delete, activate, deactivate, run, clone, get_blueprint, get_logs. No two tools appear to do the same thing.
All tool names use snake_case with a consistent verb_noun pattern (e.g., list_scenarios, create_scenario, get_data_store). There are no mixed conventions or vague verbs. The pattern extends to compound resources like create_data_store_record and list_data_store_records.
21 tools is on the heavy side for the server's scope, falling into the 16-25 borderline range. While most tools earn their place by covering distinct operations, the set could likely be consolidated without losing functionality. The count feels somewhat inflated for the core scenario and data store management tasks.
Scenario management is comprehensive (full CRUD plus activate, deactivate, run, clone, blueprint, logs). However, notable gaps exist: data stores and records lack update/delete operations, and connections and hooks are only listable with no create, update, or delete. These missing lifecycle operations will limit agents needing full management.