This Model Context Protocol (MCP) server for Make.com enables intelligent patching, scenario management, and seamless integration with Make.com automation workflows, allowing you to read and update scenario blueprints programmatically.
Before installing the MakeSync MCP Server, ensure you have:
The fastest way to get started is using the quick setup method:
MAKE_DOT_COM_API_KEY=your_api_key_here npm install && npm run build
Replace your_api_key_here
with your actual Make.com API key.
The MakeSync MCP Server provides two main tools for interacting with Make.com scenarios.
Use the read_make_dot_com_scenario_blueprint
tool to retrieve the full JSON blueprint of any scenario:
// Example of reading a scenario blueprint
const scenarioBlueprint = await read_make_dot_com_scenario_blueprint({
scenario_id: 123456, // Your scenario ID number
draft: true // Optional - set to true to read draft version
});
console.log(scenarioBlueprint); // Full blueprint JSON
Use the update_make_dot_com_scenario
tool to patch and modify scenarios:
// Example of updating a scenario
const updateResult = await update_make_dot_com_scenario({
scenario_id: 123456, // Your scenario ID
name: "Updated Scenario", // Optional - change scenario name
description: "New description", // Optional
module_id: 5, // Optional - target specific module
operations: [ // Optional - patch operations
{
path: "parameters.text",
value: "New text value"
}
],
confirm: true // Required for installing new apps
});
The server includes several intelligent patching capabilities:
{{...}}
when appropriateconfirm
parameter prevents accidental changesMakeSync MCP Server is compatible with Claude Desktop, making it easy to incorporate AI assistance in your workflow automation tasks.
When using with Claude Desktop, the server will be automatically initialized with your configured API key.
const blueprint = await read_make_dot_com_scenario_blueprint({
scenario_id: 123456
});
// Examine module structure
const modules = blueprint.blueprint.modules;
console.log(`Scenario has ${modules.length} modules`);
await update_make_dot_com_scenario({
scenario_id: 123456,
module_id: 2,
operations: [
{ path: "parameters.url", value: "https://api.example.com/v2/data" },
{ path: "parameters.headers.Authorization", value: "Bearer token123" }
]
});
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"cursor-rules-mcp": {
"command": "npx",
"args": [
"-y",
"cursor-rules-mcp"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.