MCP Scenario Builder

Feature Requests
1

I’m looking at your platform for an automation project. The execution-time pricing and JavaScript support are really compelling, but I noticed something that could be a major unlock:

Make has an unofficial MCP server that lets Claude Desktop (or any MCP-compatible client) programmatically generate and import workflow blueprints.

1. Specification-first: Teams write detailed specs (schema, error handlers, validation rules, edge cases) alongside their code

2. AI-assisted scaffolding: Claude reads the full spec and generates a complete blueprint with all domain-specific details baked in

3. Persistent context: The same Claude session can iterate and refine across multiple workflows—no loss of context between generations

4. Version control: Blueprints are importable artifacts that can be reviewed, tested, and versioned before deployment

Your in-platform AI Copilot handles single-session scaffolding well, but it can’t maintain context across iterations or access external specifications. For enterprise workflows - this context loss creates friction.

If you published an MCP server, teams could build spec-driven workflows at scale while keeping your pricing advantage.

2

It’s a great point, and it’s already in development. I hope to release it in May.

3

The introduction of the MCP scenario builder seems like a significant step forward for anyone managing intricate automation workflows. I’ve often found that as logic gets more complex, keeping everything organized becomes a real challenge. Having a dedicated tool to help structure these scenarios should definitely make the development process much smoother and more intuitive, especially when you are dealing with multiple data points simultaneously.

4

The MCP scenario builder looks like a powerful addition for structuring complex automation logic. It should make it much easier to visualize data flows and maintain clean connections between different nodes and services.