Can I use Microsoft To Do as a CLI?

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

Can I expose Microsoft To Do through MCP?

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

Where are Microsoft To Do credentials stored?

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

Can I deny write access for Microsoft To Do MCP tools?

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

productivity

Microsoft To Do CLI for CI

Use the Microsoft To Do CLI for CI with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 5 read 2 write Manual OAuth token auth

Submit Microsoft To Do feedback View package source

Microsoft To Do CLI for CI

Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status.

Use this shape when a pipeline needs to read or update an external service. The Microsoft To Do CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Microsoft To Do CLI for CI
kosmokrator integrations:configure microsoft_todo --set access_token="$MICROSOFT_TODO_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call microsoft_todo.todo_list_lists '{}' --json

Discovery Before Execution

Agents and scripts can inspect Microsoft To Do docs and schemas before choosing a function.

kosmo integrations:docs microsoft_todo --json
kosmo integrations:docs microsoft_todo.todo_list_lists --json
kosmo integrations:schema microsoft_todo.todo_list_lists --json
kosmo integrations:search "Microsoft To Do" --json
kosmo integrations:list --json

Useful Microsoft To Do CLI Functions

Function	Type	Parameters	Description
`microsoft_todo.todo_list_lists`	Read	none	List all Microsoft To Do task lists for the authenticated user. Returns the list ID, display name, and well-known name for each list.
`microsoft_todo.todo_get_list`	Read	id	Get a specific Microsoft To Do task list by its ID. Returns the list details including display name and well-known name.
`microsoft_todo.todo_create_list`	Write	displayName	Create a new Microsoft To Do task list. Provide a display name for the list.
`microsoft_todo.todo_list_tasks`	Read	list_id	List all tasks in a Microsoft To Do task list. Returns task titles, statuses, body content, and due dates.
`microsoft_todo.todo_get_task`	Read	list_id, id	Get a specific task from a Microsoft To Do task list by its ID. Returns full task details including title, body, status, due date, and importance.
`microsoft_todo.todo_create_task`	Write	list_id, title, body, due_date, due_timezone	Create a new task in a Microsoft To Do task list. Provide a title, and optionally a body and due date.
`microsoft_todo.todo_get_current_user`	Read	none	Get the authenticated Microsoft user profile. Returns display name, email, and other account details. Useful for verifying which account is connected.

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 Microsoft To Do CLI Pages

Cron Jobs Microsoft To Do CLI for cron jobs. Shell Scripts Microsoft To Do CLI for shell scripts. Headless Automation Microsoft To Do CLI for headless automation. Coding Agents Microsoft To Do CLI for coding agents.