Automatisch MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTOMATISCH_API_KEY | No | API key for authentication (optional but recommended) | |
| AUTOMATISCH_BASE_URL | No | Automatisch instance URL | http://localhost:3001 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workflowsC | List all workflows in Automatisch |
| get_workflowC | Get detailed information about a specific workflow |
| create_workflowC | Create a new workflow |
| update_workflowC | Update an existing workflow |
| delete_workflowC | Delete a workflow |
| list_connectionsB | List all app connections |
| create_connectionC | Create a new app connection |
| list_executionsB | List workflow executions |
| get_available_appsB | Get list of available apps and their capabilities |
| test_workflowC | Test a workflow with sample data |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Workflows Overview | Overview of all workflows and their status |
| App Connections | List of configured app connections |
| Available Apps | Catalog of available apps and integrations |
| Recent Executions | Recent workflow executions and their results |
TDQS
Scored across 10 tools
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.
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.
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.
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.