Complete playbook for integrating Make.com scenarios with Claude Desktop via MCP Server
Configuration
View docs{
"mcpServers": {
"joseph19820124-make-mcp-integration-playbook": {
"command": "node",
"args": [
"dist/server.js"
],
"env": {
"MAKE_API_TOKEN": "YOUR_API_TOKEN",
"MAKE_WEBHOOK_URL": "YOUR_WEBHOOK_URL_PLACEHOLDER"
}
}
}
}You set up an MCP Server that connects Make.com workflows to Claude Desktop, letting you trigger and manage automated tasks from natural language prompts. This enables seamless, AI-assisted automation across Make.com scenarios and Claude-powered how-tos, with reliable webhook-driven data flow and centralized orchestration.
You run the MCP Server locally and expose it to Claude Desktop or another MCP client. Configure your MCP client to start the server, supply the webhook URL, and then trigger workflows from Claude prompts. The server listens for Make.com webhooks and forwards data into your automation flow, allowing you to validate, transform, and route information to services like Google Sheets or Notion, while keeping the control in a unified AI-driven interface.
mkdir make-mcp-server
cd make-mcp-server
npm init -y
npm install @modelcontextprotocol/sdk axios dotenv
npm install -D typescript @types/node# Create TypeScript config file if needed (tsconfig.json should be present in the project)
# Then build and run the server
npm run build
npm startMAKE_WEBHOOK_URL=你的Make.com_webhook_URL
MAKE_API_TOKEN=你的Make.com_API_token(可选)Configuration, security, and practical usage details help you tailor the MCP Server to your workflow.
Step-by-step instructions to integrate with Claude Desktop and Make.com are provided below to ensure a smooth setup and reliable operation.
{
"mcpServers": {
"make_automation": {
"command": "node",
"args": ["dist/server.js"],
"env": {
"MAKE_WEBHOOK_URL": "你的Make.com_webhook_URL",
"MAKE_API_TOKEN": "YOUR_API_TOKEN_IF_PROVIDED"
}
}
}
}To test the integration, compile and run the server, then ensure Claude Desktop is pointed at the correct MCP server configuration and can invoke actions through the webhook URL.
Common issues include connection failures, webhook invocation errors, and data transmission problems. Verify file paths and permissions when starting the server, check that the Node.js version is compatible, confirm the webhook URL is correct, and ensure the Make.com scenario is active and can reach the MCP server.
# Enable verbose logs for debugging
DEBUG=* node dist/server.js
# Test webhook reachability
curl -X POST -H "Content-Type: application/json" -d '{"test":true}' YOUR_WEBHOOK_URL