create_connection
Create a new app connection
LABSCO SUMMARY
A workflow can be built inactive, exercised with sample data, and only then switched on.
The active flag is a parameter on both creation and update, and test_workflow takes its own test data, so the path from draft to live never leaves the tools. When something stops firing, list_executions filters by workflow and by status, which is where the failure is identified rather than in the interface. Connections hold the credentials for the apps a workflow talks to, and the available-apps catalogue is what tells you which app keys exist to connect.
What it is
A client for a self-hosted Automatisch instance covering workflows, app connections and execution history.
What you get
- Workflows listed by status with a limit, fetched by ID, created, updated and deleted.
- An active flag set at creation or afterwards, so a workflow can exist before it is allowed to run.
- App connections listed by app key and created with their credentials, against the catalogue of available apps and their capabilities.
- Execution history filtered by workflow and status, and a test run against sample data you supply.
Requirements
A running Automatisch instance, its address in AUTOMATISCH_BASE_URL, and an API key in AUTOMATISCH_API_KEY.
Setup effort
One command plus a key — npx -y automatisch-mcp-server, then supply credentials
USE CASES
01
Taking a workflow from draft to running without opening the browser
Creating it inactive, exercising it with sample data and then activating it is three calls in the same conversation.
02
Finding out why an automation stopped firing
Execution history filtered by workflow and status is where a silent failure becomes visible.
03
Connecting an app before a workflow can reach it
A workflow can only use apps that already have a connection, and the app key comes from the catalogue rather than from memory.
10 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_workflow
Create a new workflow
delete_workflow
Delete a workflow
get_available_apps
Get list of available apps and their capabilities
get_workflow
Get detailed information about a specific workflow
list_connections
List all app connections
list_executions
List workflow executions
list_workflows
List all workflows in Automatisch
test_workflow
Test a workflow with sample data
update_workflow
Update an existing workflow
BEFORE YOU INSTALL
What to know first
Tools you get
10 tools when we connected. create_workflow, update_workflow, delete_workflow, test_workflow and create_connection change your instance; delete_workflow removes a workflow outright.
Requires
- npx on PATH
- Node.js 18+
- AUTOMATISCH_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 10 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y automatisch-mcp-serverMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"automatisch": {
"command": "npx",
"args": [
"-y",
"automatisch-mcp-server"
],
"env": {
"AUTOMATISCH_BASE_URL": "http://localhost:3001",
"AUTOMATISCH_API_KEY": "<YOUR_AUTOMATISCH_API_KEY>"
}
}
}
}
