Skip to main content
Glama

Automatisch MCP Server

npm version npm downloads bundle size

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

Overview

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.

Related MCP server: n8n Workflow Builder

Features

Tools Available

  • Workflow Management: Create, read, update, delete, and test workflows

  • Connection Management: Manage app connections and credentials

  • Execution Monitoring: View workflow execution history and status

  • App Discovery: Browse available apps and their capabilities

  • Testing: Test workflows with sample data

Resources Provided

  • Workflows overview with status summary

  • App connections listing

  • Available apps catalog

  • Recent executions log

Prerequisites

  • Node.js 18+

  • Running Automatisch instance

  • Automatisch API access (API key recommended)

Installation

  1. Clone or download the MCP server code

  2. Install dependencies:

    npm install
  3. Build the project:

    npm run build

Configuration

Set environment variables:

# Automatisch instance URL (default: http://localhost:3001)
export AUTOMATISCH_BASE_URL="http://your-automatisch-instance:3001"

# API key for authentication (optional but recommended)
export AUTOMATISCH_API_KEY="your-api-key"

Usage

Claude Desktop Integration

Add to your Claude Desktop configuration file:

{
  "mcpServers": {
    "automatisch": {
      "command": "npx",
      "args": ["-y", "automatisch-mcp-server"],
      "env": {
        "AUTOMATISCH_BASE_URL": "http://localhost:3001",
        "AUTOMATISCH_API_KEY": "your-api-key"
      }
    }
  }
}

Standalone Usage

npm start

Available Tools

Workflow Management

  • list_workflows - List all workflows with optional filtering

  • get_workflow - Get detailed workflow information

  • create_workflow - Create new workflow

  • update_workflow - Update existing workflow

  • delete_workflow - Delete workflow

  • test_workflow - Test workflow with sample data

Connection Management

  • list_connections - List app connections

  • create_connection - Create new app connection

Monitoring & Discovery

  • list_executions - View workflow execution history

  • get_available_apps - Browse available apps and integrations

Example Usage with AI Assistant

# List all active workflows
"Show me all active workflows"

# Create a new workflow
"Create a workflow named 'Email Notifications' that sends emails when new GitHub issues are created"

# Check recent executions
"Show me the recent workflow executions and their status"

# Get workflow details
"Tell me about the workflow with ID 'abc123'"

# List available apps
"What apps are available for integration?"

API Endpoints

The server interfaces with these Automatisch API endpoints:

  • GET /api/flows - List workflows

  • POST /api/flows - Create workflow

  • PATCH /api/flows/:id - Update workflow

  • DELETE /api/flows/:id - Delete workflow

  • GET /api/connections - List connections

  • POST /api/connections - Create connection

  • GET /api/executions - List executions

  • GET /api/apps - List available apps

Development

Running in Development Mode

npm run dev

Building

npm run build

Cleaning Build Files

npm run clean

Error Handling

The server includes comprehensive error handling:

  • Network connectivity issues with Automatisch

  • Invalid API responses

  • Missing required parameters

  • Authentication failures

Errors are logged and returned as structured responses to the AI assistant.

Security Considerations

  • Use API keys for authentication when available

  • Ensure Automatisch instance is properly secured

  • Limit network access to trusted sources

  • Regularly update dependencies

Troubleshooting

Common Issues

  1. Connection Failed: Verify AUTOMATISCH_BASE_URL is correct and accessible

  2. Authentication Error: Check AUTOMATISCH_API_KEY is valid

  3. Tool Not Found: Ensure MCP server is properly registered with Claude Desktop

  4. API Errors: Check Automatisch logs for detailed error information

Debug Mode

Enable debug logging by setting:

export NODE_ENV=development

Contributing

  1. Fork the repository

  2. Create a feature branch

  3. Make your changes

  4. Add tests if applicable

  5. Submit a pull request

License

This project is licensed under the MIT License.

Support

For issues related to:

Available Tools

10 tools
create_connectionC

Create a new app connection

Inputs: appKey (required), name (required), credentials (required).

create_workflowC

Create a new workflow

Inputs: name (required), description, active.

delete_workflowC

Delete a workflow

Inputs: workflowId (required).

get_available_appsB

Get list of available apps and their capabilities

Inputs: category.

get_workflowC

Get detailed information about a specific workflow

Inputs: workflowId (required).

list_connectionsB

List all app connections

Inputs: appKey.

list_executionsB

List workflow executions

Inputs: workflowId, status, limit.

list_workflowsC

List all workflows in Automatisch

Inputs: status, limit.

test_workflowC

Test a workflow with sample data

Inputs: workflowId (required), testData.

update_workflowC

Update an existing workflow

Inputs: workflowId (required), name, description, active.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting specific resources and actions: connections, workflows, executions, and apps. There is no overlap or ambiguity, with tools like create_workflow, update_workflow, and delete_workflow covering different lifecycle stages without confusion.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case throughout, such as create_connection, list_workflows, and update_workflow. The naming is predictable and uniform, making it easy for agents to understand and select tools.

    Tool Count5/5

    With 10 tools, the count is well-scoped for managing workflows, connections, and executions in an automation platform. Each tool serves a clear purpose, such as CRUD operations for workflows and monitoring executions, without being excessive or insufficient.

    Completeness4/5

    The toolset provides strong coverage for core workflow management, including create, read, update, delete, list, and test operations, along with connection handling and execution monitoring. A minor gap exists in lacking tools for updating or deleting connections, but agents can still perform essential tasks effectively.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      F
      maintenance
      Connects AI assistants (Claude, Cursor, etc.) directly to the HiveFlow automation platform, allowing them to create, manage, and execute automation flows through natural language commands.
      9
      4 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI models to manage n8n workflow automation through a standardized interface. Supports creating, reading, updating, and deleting workflows with comprehensive access to workflow nodes, connections, and configurations.
      68 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to programmatically control n8n via natural language for automated workflow creation, modification, and execution management.
      1
      -