Skip to main content
Glama
yuli-tonkin-bg

Make MCP Server

by yuli-tonkin-bg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Make MCP Server

No user-submitted related servers found.

    Related Servers

    • Make.com MCP Server

      Joseph19820124
      A
      license
      B
      quality
      D
      maintenance
      Enables Claude Desktop to trigger and interact with Make.com automation scenarios through webhooks. Allows users to execute complex workflows and integrations with third-party services like Google Sheets, Notion, and Slack using natural language commands.
      3
      96 npm
      MIT

    • Make MCP Server

      3rzy
      A
      license
      Not graded
      quality
      D
      maintenance
      An 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.
      96 npm
      MIT

    • Make MCP Server

      integromat
      A
      license
      D
      quality
      F
      maintenance
      Transform 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.
      6
      44 npm
      172
      MIT

    • Make MCP Server

      forayconsulting
      A
      license
      Not graded
      quality
      D
      maintenance
      This server enables AI assistants to discover, parameterize, and trigger Make.com automation workflows configured for on-demand execution. It allows users to execute scenarios and receive structured JSON results, bridging the gap between AI assistants and complex automation ecosystems.
      44 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 26 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action: scenarios, executions, data stores, webhooks, connections, and org/team listing are clearly separated. Even related tools like make_run_scenario vs make_trigger_webhook are distinguishable by their mechanism and descriptions.

    Naming Consistency5/5

    All tools follow a consistent make_verb_noun snake_case pattern. Singular 'get' for single items and plural 'list' for collections is applied uniformly. The only slight outlier is make_open_in_browser, but it still fits the make_ prefix convention.

    Tool Count4/5

    At 26 tools, it's slightly above the 'heavy' range, but the count is justified by the broad scope of Make.com management: scenarios, executions, DLQ, data stores, webhooks, and connections each require several dedicated operations. No tool feels redundant.

    Completeness3/5

    Scenario execution and DLQ handling are well covered, and data store record CRUD exists. However, there are notable gaps: no scenario create/delete, no data store create/update/delete, and no webhook create/delete. These are obvious lifecycle operations for the domain and would require workarounds.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources