This MCP server integrates with the Make.com API to read Make resources, such as scenario blueprints. The server exposes a tool named read_make_dot_com_scenario_blueprint which retrieves the JSON blueprint for a given scenario. To use it, start the MCP server using the provided node entry point, ensuring your Make.com API key and base URL are supplied via environment variables. When invoking the read_make_dot_com_scenario_blueprint tool, provide the required inputs: scenario_id (a numeric ID for the Make scenario) and an optional draft flag. If draft is true, the draft blueprint is retrieved; if false or omitted, the live blueprint is returned. If a blueprintId is supplied in the query as well, the draft parameter is ignored. This allows you to inspect and integrate Make.com scenario blueprints into your workflows via MCP.

Prerequisites:

• Node.js (recommended LTS) and npm installed
• Access to the repository containing the MCP server code

Installation steps:

1. Clone the repository: git clone https://github.com/your-organization/mcp-server-make-dot-com.git cd mcp-server-make-dot-com

2. Install dependencies: npm install

3. Build/run setup (if required by the project): npm run build

   Ensure dist/index.js exists after build

4. Create the configuration for your MCP runner as shown in the example configuration, replacing paths with your actual paths to dist/index.js and providing your Make.com credentials.

5. Run the MCP server entry point with your environment variables set, e.g.: MAKE_DOT_COM_API_KEY=your-api-key MAKE_DOT_COM_BASE_URL=eu2.make.com node dist/index.js

6. Verify the server starts and is reachable by your MCP orchestration system.

Notes and tips:

• Ensure the API key you provide has the necessary scopes listed in the README (agents:read, apps:read, connections:read, custom-property-structures:read, datastores:read, devices:read, scenarios:read, scenarios:run, scenarios:write, teams:read).
• The base URL should correspond to the location of your Make.com instance (e.g., eu2.make.com or make.com, depending on your region).
• If you encounter authentication issues, double-check that MAKE_DOT_COM_API_KEY is properly passed to the process environment where the MCP server runs.
• The read_make_dot_com_scenario_blueprint tool expects scenario_id (number) and optional draft (boolean). Use draft=true to fetch the draft blueprint, otherwise use the live blueprint.
• When deploying in production, consider wrapping the MCP process in a process manager and securing environment variables via your deployment platform.