KosmoKrator

productivity

MeisterTask CLI for AI Agents

Use the MeisterTask CLI from KosmoKrator to call MeisterTask tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

MeisterTask CLI Setup

MeisterTask can be configured headlessly with `kosmokrator integrations:configure meistertask`.

Install, configure, and verify 
# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure meistertask --set access_token="$MEISTERTASK_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor meistertask --json
kosmokrator integrations:status --json

Credentials

Authentication type: Bearer token bearer_token. Configure credentials once, then reuse the same stored profile from scripts, coding CLIs, Lua, and MCP.

KeyEnv varTypeRequiredLabel
access_token MEISTERTASK_ACCESS_TOKEN Secret secret yes Access Token
url MEISTERTASK_URL URL url no API Base URL

Command Patterns

The generic command is stable across every integration. The provider shortcut is shorter for humans.

Generic CLI call 
kosmo integrations:call meistertask.meistertask_list_projects '{}' --json
Provider shortcut 
kosmo integrations:meistertask meistertask_list_projects '{}' --json

Discovery

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

Discovery commands 
kosmo integrations:docs meistertask --json
kosmo integrations:docs meistertask.meistertask_list_projects --json
kosmo integrations:schema meistertask.meistertask_list_projects --json
kosmo integrations:search "MeisterTask" --json
kosmo integrations:list --json

Automation Contexts

The same configured command surface works in these environments. The command does not change unless the host wrapper, credentials, or permissions change.

CI Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status. Cron Jobs Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config. Shell Scripts Call integration functions from shell scripts with stable JSON input and output. Headless Automation Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers. Coding Agents Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

CLI Functions

Every function below can be called headlessly. Commands are highlighted, copyable, and scroll horizontally when payloads are long.

meistertask.meistertask_list_projects

List all MeisterTask projects the authenticated user has access to. Returns project IDs, names, and basic metadata.

Read read
Parameters
none
Generic call 
kosmo integrations:call meistertask.meistertask_list_projects '{}' --json
Shortcut 
kosmo integrations:meistertask meistertask_list_projects '{}' --json

meistertask.meistertask_get_project

Get detailed information about a specific MeisterTask project, including sections, members, and status.

Read read
Parameters
id
Generic call 
kosmo integrations:call meistertask.meistertask_get_project '{"id":1}' --json
Shortcut 
kosmo integrations:meistertask meistertask_get_project '{"id":1}' --json

meistertask.meistertask_create_task

Create a new task in a MeisterTask project. You must specify the project and at least a task name. Optionally set status, assignee, due date, description, and more.

Write write
Parameters
project_id, name, status, description, assignee_id, due_date, priority, section_id, labels
Generic call 
kosmo integrations:call meistertask.meistertask_create_task '{"project_id":1,"name":"example_name","status":"example_status","description":"example_description","assignee_id":1,"due_date":"example_due_date","priority":1,"section_id":1}' --json
Shortcut 
kosmo integrations:meistertask meistertask_create_task '{"project_id":1,"name":"example_name","status":"example_status","description":"example_description","assignee_id":1,"due_date":"example_due_date","priority":1,"section_id":1}' --json

meistertask.meistertask_list_tasks

List tasks across MeisterTask projects with optional filters. Supports filtering by project, status, assignee, and more.

Read read
Parameters
project_id, status, assignee_id, limit, page
Generic call 
kosmo integrations:call meistertask.meistertask_list_tasks '{"project_id":1,"status":"example_status","assignee_id":1,"limit":1,"page":1}' --json
Shortcut 
kosmo integrations:meistertask meistertask_list_tasks '{"project_id":1,"status":"example_status","assignee_id":1,"limit":1,"page":1}' --json

meistertask.meistertask_get_task

Get detailed information about a specific MeisterTask task, including its description, status, assignee, due date, and attachments.

Read read
Parameters
id
Generic call 
kosmo integrations:call meistertask.meistertask_get_task '{"id":1}' --json
Shortcut 
kosmo integrations:meistertask meistertask_get_task '{"id":1}' --json

meistertask.meistertask_update_task

Update an existing MeisterTask task. You can change the name, status, description, assignee, due date, priority, labels, and more.

Write write
Parameters
id, name, status, description, assignee_id, due_date, priority, section_id, labels
Generic call 
kosmo integrations:call meistertask.meistertask_update_task '{"id":1,"name":"example_name","status":"example_status","description":"example_description","assignee_id":1,"due_date":"example_due_date","priority":1,"section_id":1}' --json
Shortcut 
kosmo integrations:meistertask meistertask_update_task '{"id":1,"name":"example_name","status":"example_status","description":"example_description","assignee_id":1,"due_date":"example_due_date","priority":1,"section_id":1}' --json

meistertask.meistertask_get_current_user

Get the profile of the currently authenticated MeisterTask user, including name, email, and account details.

Read read
Parameters
none
Generic call 
kosmo integrations:call meistertask.meistertask_get_current_user '{}' --json
Shortcut 
kosmo integrations:meistertask meistertask_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

meistertask.meistertask_list_projects 0 parameters
Schema command 
kosmo integrations:schema meistertask.meistertask_list_projects --json
ParameterTypeRequiredDescription
No parameters.
meistertask.meistertask_get_project 1 parameters
Schema command 
kosmo integrations:schema meistertask.meistertask_get_project --json
ParameterTypeRequiredDescription
id integer yes The project ID.
meistertask.meistertask_create_task 9 parameters
Schema command 
kosmo integrations:schema meistertask.meistertask_create_task --json
ParameterTypeRequiredDescription
project_id integer yes The project ID to create the task in.
name string yes The task name / title.
status string no Task status. Common values: "open", "completed". Defaults to "open".
description string no A detailed description of the task (supports Markdown).
assignee_id integer no The user ID of the person to assign the task to.
due_date string no Due date in ISO 8601 format (e.g., "2026-04-30").
priority integer no Task priority level.
section_id integer no The section (column) ID within the project to place the task.
labels array no Array of label names or IDs to attach to the task.
meistertask.meistertask_list_tasks 5 parameters
Schema command 
kosmo integrations:schema meistertask.meistertask_list_tasks --json
ParameterTypeRequiredDescription
project_id integer no Filter tasks by project ID.
status string no Filter by status. Common values: "open", "completed".
assignee_id integer no Filter by assignee user ID.
limit integer no Maximum number of tasks to return.
page integer no Page number for pagination.
meistertask.meistertask_get_task 1 parameters
Schema command 
kosmo integrations:schema meistertask.meistertask_get_task --json
ParameterTypeRequiredDescription
id integer yes The task ID.
meistertask.meistertask_update_task 9 parameters
Schema command 
kosmo integrations:schema meistertask.meistertask_update_task --json
ParameterTypeRequiredDescription
id integer yes The task ID to update.
name string no New task name / title.
status string no New status. Common values: "open", "completed".
description string no Updated task description (supports Markdown).
assignee_id integer no User ID to reassign the task to.
due_date string no Updated due date in ISO 8601 format (e.g., "2026-04-30").
priority integer no Updated priority level.
section_id integer no Move the task to a different section (column).
labels array no Updated array of label names or IDs.
meistertask.meistertask_get_current_user 0 parameters
Schema command 
kosmo integrations:schema meistertask.meistertask_get_current_user --json
ParameterTypeRequiredDescription
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.