Model Context Protocol moderate risk

Make

Exposes Make scenarios as callable tools for AI assistants, enabling integration with Make automation workflows via API key authentication.

Connections & Capabilities

Connects To

GitHubTwitter

Capabilities

readwriteexec

Quickstart

Config

{
    "mcpServers": {
        "make": {
            "command": "npx",
            "args": ["-y", "@makehq/mcp-server"],
            "env": {
                "MAKE_API_KEY": "<your-api-key>",
                "MAKE_ZONE": "<your-zone>",
                "MAKE_TEAM": "<your-team-id>"
            }
        }
    }
}

Exposed MCP Tools (1)

moderate

invoke_scenario

Executes a specified Make scenario with provided parameters and returns the output.

Scenarios can perform write operations or interact with external services.

Safety Assessment

This MCP server is reasonably safe if the Make scenarios are designed with security in mind and the API key is protected. Risks increase if scenarios perform sensitive operations or interact with untrusted external services. Regularly audit Make scenarios for potential security vulnerabilities.

Requires API key for authentication.
Scenarios are pre-defined in Make, limiting ad-hoc code execution.
Returns structured JSON output, aiding in predictable AI interpretation.
Access is limited by the API key's scopes (scenarios:read, scenarios:run).

API key compromise could allow unauthorized scenario execution.
Scenarios can potentially perform write operations or access external services.
No built-in input validation beyond what's defined in the Make scenario.
Lack of sandboxing for scenario execution.