Make

🚀 Problem Description: Integration Issues between Make and Claude via MCP Protocol

This project aims to integrate Make and Claude Desktop using the Model Context Protocol (MCP), but has encountered connection problems.

🚀 Quick Start

This README details the issues encountered during the integration of Make and Claude Desktop using the MCP protocol, the work completed, the problems faced, and requests for help.

✨ Features

• Built a Node.js-based Make MCP server from scratch, enabling communication with the Make API and Claude Desktop, supporting the JSON - RPC 2.0 protocol, and providing various tools for managing Make scenarios.
• Tested multiple configurations, including different ports, communication methods, and configuration options in the claude_desktop_config.json file.

📦 Installation

N/A

💻 Usage Examples

N/A

📚 Documentation

Background

I attempted to create an integration between Make (formerly Integromat) and Claude Desktop using the Model Context Protocol (MCP). Despite various attempts and modifications, I was unable to establish a proper connection.

Completed Work

1. Built a Node.js-based Make MCP server from scratch with the following features:
   • Communication with the Make API.
   • Communication with Claude Desktop using the WebSocket protocol.
   • Support for the JSON - RPC 2.0 protocol as required by MCP.
   • Various tools for managing Make scenarios.
2. Tried multiple configurations:
   • Different ports (3000, 3001, 3333, 5555).
   • Different communication methods (REST API, WebSocket).
   • Different configuration options in the claude_desktop_config.json file.
   • Both automatic and manual server startup.

Encountered Problems

1. Port Conflict Issue: Claude Desktop attempted to start its own instance on the same port, resulting in the following error:

   Error: listen EADDRINUSE: address already in use :::3001
   

2. Protocol Compatibility Issue: Despite the server implementing the JSON - RPC 2.0 protocol, Claude still displayed the following error message:

   [Error message example]
   

3. WebSocket Connection Issue: After trying multiple configurations, a stable WebSocket connection could not be established.

Detailed Technical Information

Server Code

// Omit code description, please refer to the English version.

Claude Desktop Configuration

Tried the following configurations:

"make": {
  "command": "node",
  "args": ["/Users/krzyk/google-workspace-mcp/make-mcp-server/make-mcp-server.js"],
  "env": {
    "MAKE_API_TOKEN": "[token]",
    "PORT": "3001"
  },
  "url": "ws://localhost:3001",
  "disabled": true
}

And a simpler version:

"make": {
  "disabled": true,
  "url": "ws://localhost:5555"
}

Questions and Request for Help

1. Is there detailed MCP protocol documentation available to understand the expected communication format?
2. Has anyone had experience integrating a custom MCP server with Claude Desktop?
3. Are there any special requirements for WebSocket or JSON - RPC 2.0 that are not obvious?
4. Are there any official tools or libraries to help create a compatible MCP server?

Any suggestions would be highly appreciated. I've temporarily switched to using n8n, which already has a ready - made MCP server implementation, but I'm still interested in solving this problem for Make.

🔧 Technical Details

The project involves building a custom MCP server based on Node.js, which needs to communicate with the Make API and Claude Desktop. It uses the WebSocket protocol and the JSON - RPC 2.0 protocol. However, issues such as port conflicts, protocol compatibility, and WebSocket connection stability have arisen during the integration process.

📄 License

N/A