Can I use MeisterTask as a CLI?

Yes. KosmoKrator exposes a MeisterTask CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose MeisterTask through MCP?

Yes. The KosmoKrator MCP gateway can expose selected MeisterTask tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are MeisterTask credentials stored?

MeisterTask credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for MeisterTask MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

MeisterTask CLI for Shell Scripts

Use the MeisterTask CLI for shell scripts with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 5 read 2 write Bearer token auth

Submit MeisterTask feedback View package source

MeisterTask CLI for Shell Scripts

Call integration functions from shell scripts with stable JSON input and output.

Use shell scripts for small local automations that need one or more integration calls. The MeisterTask CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# MeisterTask CLI for Shell Scripts
kosmokrator integrations:configure meistertask --set access_token="$MEISTERTASK_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call meistertask.meistertask_list_projects '{}' --json

Discovery Before Execution

Agents and scripts can inspect MeisterTask docs and schemas before choosing a function.

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

Useful MeisterTask CLI Functions

Function	Type	Parameters	Description
`meistertask.meistertask_list_projects`	Read	none	List all MeisterTask projects the authenticated user has access to. Returns project IDs, names, and basic metadata.
`meistertask.meistertask_get_project`	Read	id	Get detailed information about a specific MeisterTask project, including sections, members, and status.
`meistertask.meistertask_create_task`	Write	project_id, name, status, description, assignee_id, due_date, priority, section_id, labels	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.
`meistertask.meistertask_list_tasks`	Read	project_id, status, assignee_id, limit, page	List tasks across MeisterTask projects with optional filters. Supports filtering by project, status, assignee, and more.
`meistertask.meistertask_get_task`	Read	id	Get detailed information about a specific MeisterTask task, including its description, status, assignee, due date, and attachments.
`meistertask.meistertask_update_task`	Write	id, name, status, description, assignee_id, due_date, priority, section_id, labels	Update an existing MeisterTask task. You can change the name, status, description, assignee, due date, priority, labels, and more.
`meistertask.meistertask_get_current_user`	Read	none	Get the profile of the currently authenticated MeisterTask user, including name, email, and account details.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related MeisterTask CLI Pages

CI MeisterTask CLI for CI. Cron Jobs MeisterTask CLI for cron jobs. Headless Automation MeisterTask CLI for headless automation. Coding Agents MeisterTask CLI for coding agents.