Automatisch MCP Server

Connect Automatisch to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP Server for Automatisch workflow automation platform. The automatisch mcp server is what makes that connection.

What the server does

A Model Context Protocol (MCP) server that provides AI assistants with access to Automatisch workflow automation capabilities.

This MCP server enables AI assistants to interact with Automatisch, an open-source Zapier alternative for workflow automation. It provides tools to manage workflows, connections, executions, and app integrations.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Testing — Test workflows with sample data
• Building — The Building tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: AUTOMATISCH_BASE_URL, AUTOMATISCH_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Node.js 18+ - Running Automatisch instance - Automatisch API access (API key recommended)

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Automatisch's toolset — Testing, Building — is a fair guide to whether it matches your workflow. It is maintained by milisp; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.