Can I use Motion as a CLI?

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

Can I expose Motion through MCP?

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

Where are Motion credentials stored?

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

Can I deny write access for Motion MCP tools?

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

productivity

Motion CLI for Headless Automation

Use the Motion CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write Bearer token auth

Submit Motion feedback View package source

Motion CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Motion CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Motion CLI for Headless Automation
kosmokrator integrations:configure motion --set access_token="$MOTION_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call motion.motion_list_tasks '{"status":"example_status","projectId":"example_projectId","assigneeId":"example_assigneeId","limit":1,"cursor":"example_cursor"}' --json

Discovery Before Execution

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

kosmo integrations:docs motion --json
kosmo integrations:docs motion.motion_list_tasks --json
kosmo integrations:schema motion.motion_list_tasks --json
kosmo integrations:search "Motion" --json
kosmo integrations:list --json

Useful Motion CLI Functions

Function	Type	Parameters	Description
`motion.motion_list_tasks`	Read	status, projectId, assigneeId, limit, cursor	List tasks from Motion with optional filters. Filter by status, project, or assignee. Supports cursor-based pagination.
`motion.motion_get_task`	Read	taskId	Get details of a specific task in Motion by its ID. Returns the task name, description, status, assignee, due date, priority, and project.
`motion.motion_create_task`	Write	name, projectId, assigneeId, dueDate, priority, description	Create a new task in Motion. Requires a task name. Optionally specify a project, assignee, due date, priority, and description. Motion will auto-schedule the task based on priorities and deadlines.
`motion.motion_list_projects`	Read	none	List all projects in Motion. Returns project IDs, names, and other metadata. Use project IDs to filter tasks or create tasks in specific projects.
`motion.motion_get_project`	Read	projectId	Get details of a specific project in Motion by its ID. Returns the project name, description, status, and other metadata.
`motion.motion_list_schedules`	Read	startDate, endDate	List schedules from Motion within a date range. Returns scheduled tasks and events for the authenticated user.
`motion.motion_get_current_user`	Read	none	Get the profile of the currently authenticated Motion user. Returns user ID, name, email, and other 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 Motion CLI Pages

CI Motion CLI for CI. Cron Jobs Motion CLI for cron jobs. Shell Scripts Motion CLI for shell scripts. Coding Agents Motion CLI for coding agents.