概览
What is Make MCP Server (legacy)?
Make MCP Server (legacy) is a Model Context Protocol server that connects to a Make account and exposes Make scenarios configured with "On-Demand" scheduling as callable tools for AI assistants. It parses scenario input parameters and returns structured JSON output, enabling AI systems to trigger and interact with automation workflows.
How to use Make MCP Server (legacy)?
Install via npx and configure in an MCP client such as Claude Desktop. Add a JSON entry to the client’s configuration with the command npx -y @makehq/mcp-server and three required environment variables: MAKE_API_KEY, MAKE_ZONE, and MAKE_TEAM. Prerequisites include NodeJS and a Make API key with scenarios:read and scenarios:run scopes.
Key features of Make MCP Server (legacy)
- Connects to Make account and identifies On-Demand scenarios
- Parses and resolves input parameters for each scenario
- Allows AI assistants to invoke scenarios with appropriate parameters
- Returns scenario output as structured JSON
- Enables bidirectional communication between AI and automation workflows
Use cases of Make MCP Server (legacy)
- Trigger Make automation workflows directly from AI assistant conversations
- Expose complex Make automation logic as callable tools for AI assistants
- Enable AI to request data processing or actions via Make scenarios
- Create bidirectional communication between AI assistants and existing automation systems
FAQ from Make MCP Server (legacy)
What are the prerequisites for Make MCP Server (legacy)?
NodeJS, an MCP client (like the Claude Desktop app), and a Make API key with scenarios:read and scenarios:run scopes.
How do I configure Make MCP Server (legacy)?
Add a JSON entry under mcpServers in your client’s configuration. Use the command npx -y @makehq/mcp-server and set the environment variables MAKE_API_KEY, MAKE_ZONE, and MAKE_TEAM.
Is this the recommended version?
No. A modern, cloud-based version of the Make MCP Server is now available and is recommended for most use cases.
Which scenarios can be used as tools?
Only Make scenarios with “On-Demand” scheduling are identified and exposed as tools.
What output format does the server return?
The server returns scenario output as structured JSON,
