Vikunja Tasks Connector

Connect a user's Vikunja instance via username + password. The password is forwarded to the backend service once, exchanged for a long-lived Personal Access Token, and discarded. Only the encrypted PAT is stored. Returns base_url + username on success.

Advanced connect: user pastes a pre-existing Vikunja Personal Access Token (Settings → API tokens in their Vikunja UI). The PAT is encrypted on bridge and stored at rest.

Disconnect from the user's Vikunja: revoke the stored API token in their instance and delete the local connection record.

Check whether the user has a Vikunja connected (read-only — never echoes the API token). Returns connected: bool plus base_url and username when connected.

Create a new task in a project. Pass project_name (e.g. 'webhostmost tasks') or project_id. The assignee field handles assignment internally — do NOT add a separate assign_task step. priority must be an integer: 0=none 1=low 2=medium 3=high 4=urgent 5=critical. due_date must be full ISO 8601 with time (e.g. '2026-06-15T00:00:00Z'), never a bare date.

Update any fields of a task (title, description, due_date, priority, percent_done, bucket, etc.).

Mark a task as done (done=true, percent_done=1.0).

Reopen a task — mark it as not done (done=false, percent_done=0). Inverse of complete_task.

Permanently delete a task. Cannot be undone.

Delete multiple tasks at once. Pass task_ids (list of integers) OR task_titles (list of names). When using task_titles, optionally pass project_name to narrow the search. Use when user asks to delete 2+ tasks in one request.

Mark MULTIPLE tasks as done at once. Pass task_ids (list of integers) OR task_titles (list of names). When using task_titles, optionally pass project_name to narrow the search. Use when the user asks to complete/close 2+ tasks in one request.

Create a subtask under a parent task. Returns the new subtask's task_id.

List all subtasks of a given task, including their done/pending status.

Check or uncheck a TipTap checklist item in a task description. Use item_index (0-based) from the visible checklist order.

Get full details of a single task by ID: title, description, done status, due date, priority, assignees, labels, and project. Use this to verify task state before updating, or when user asks about a specific task.

Create a new project (kanban board). Returns project_id.

Update project title, description, or color.

Archive a project (is_archived=true) — hide from active views but keep data.

Permanently delete a project with all its tasks. Cannot be undone.

List all labels on this Vikunja instance. Returns label_id and title. Call this first when the user refers to a label by name — then use the returned label_id in add_label.

Create a new label with title and optional hex color. Returns label_id.

Permanently delete a label — removes it from all tasks.

List all active (non-archived) projects. Returns project_id and title. ALWAYS call this first when the user refers to a project by name — then use the returned project_id in list_project_buckets, filter_tasks, or create_task.

List kanban columns (buckets) for a project — their names, IDs, and task counts. Use ONLY when the user asks WHAT BUCKETS OR COLUMNS EXIST in a project. Does NOT return task content — use get_bucket_tasks for that. Pass project_name (e.g. 'webhostmost tasks') OR project_id.

Get tasks from a specific kanban bucket/column. Use when the user asks WHAT TASKS ARE IN a named bucket (e.g. 'what tasks are in Backlog?', 'show me the To-Do column', 'tasks in Corporate Tasks bucket'). Do NOT use to list all buckets — use list_project_buckets for that. Pass bucket_name (resolved automatically) OR bucket_id. project_name and project_id are optional — omit to search across all projects.

Count tasks in every kanban bucket for a project — returns per-bucket totals (total, done, pending) and project-level totals. Use when the user asks 'how many tasks', 'сколько задач', 'how many tasks are in each bucket', 'total tasks in project X', 'сколько всего задач'. Pass project_name (e.g. 'WebHostMost Tasks') or project_id. Counts are exact — queried directly from the database, no pagination limits.

Rename a kanban bucket (column) or update its WIP limit. Requires project_id and bucket_id — use list_project_buckets() first if you only know the bucket name.

Create a new kanban column (bucket) in a project. Requires project_id — use list_projects() first if you only know the project name. Optional WIP limit: 0 means no limit.

Delete a kanban column (bucket) from a project. Irreversible — tasks in the deleted column are moved to the project's default column, not deleted. Requires project_id and bucket_id — call list_project_buckets() first if you only know the name.

List tasks in a specific project (paginated — default 50/page, max 200). Use when the user wants to SEE task titles/details, NOT to count tasks. For counting ('how many tasks', 'сколько задач') use count_tasks_per_bucket instead — this function returns a page, not the total. Pass project_name (e.g. 'WebHostMost Tasks') or project_id.

Get metadata for a single project — id, title, description, color, archived status. Pass project_id OR project_name (e.g. 'WebHostMost Tasks'). Use when user asks about a specific project or you need its ID from a name.

Permanently delete MULTIPLE projects at once, each with ALL its tasks. Pass project_ids (list of integers) OR project_names (list of names). Requires an explicit confirm=true on a second call; the first call only previews which projects would be deleted. Cannot be undone.

Assign a person to a task. Pass task_name + assignee_query directly — do NOT call find_task or get_named_bucket_tasks first. If multiple tasks share the same name, also pass bucket_name to pick the right one. The bridge resolves assignee_query (name or email) to a Vikunja user ID automatically.

Remove a Vikunja user (by integer user ID) from a task's assignee list.

Attach an existing label (by integer label_id) to a task (by integer task_id). If you only know the label name, call create_label or ask the user for the numeric label_id — Vikunja addresses labels by ID, never by name.

Detach a label (by integer label_id) from a task (by integer task_id).

Set or change due date of a task. Pass integer task_id and due_date as ISO 8601 UTC string (e.g. '2026-04-25T12:00:00Z'). Convert relative dates ('Friday', 'tomorrow') in user's timezone first.

Set task priority — integer 0 (none) to 5 (critical). Pass integer task_id.

Move a task to another project. Pass integer task_id and integer project_id, or pass project_name (e.g. 'webhostmost tasks') to resolve automatically.

Move a task to another kanban bucket (column). Pass integer task_id and integer bucket_id, or pass bucket_name + project_name (e.g. 'To-Do', 'webhostmost tasks') to resolve automatically.

Search for Vikunja users by name or email fragment — use this before assign_task to discover who is available, or when the user asks who they can assign tasks to. Pass empty query to list all known users on the Vikunja instance.

List the members of a specific project (its assignable users — owner plus user/team shares). Use this when the user asks who is on a named project, e.g. 'who is on the WebHostMost Tasks team', 'участники проекта X', 'кто работает над проектом'. Pass project_name when you only know the name; it is resolved automatically. Prefer this over search_vikunja_users when the user names a project — it is project-scoped rather than instance-wide.

Move MULTIPLE tasks to the same kanban bucket (column) at once. Pass task_ids (list of integers) OR task_titles (list of names), plus bucket_id OR bucket_name + project_name. Use when the user asks to move 2+ tasks to a column in one request.

List tasks with optional Vikunja filter syntax. Examples: `done = false`, `priority >= 3 && due_date < now + 7d`.

List all overdue tasks (done=false AND due_date in the past).

List tasks due today (done=false AND due_date between start-of-day and end-of-day).

List tasks due in the next 7 days (done=false AND due_date between now and now+7d).

Search tasks by title substring. Returns matching tasks with their integer task_id and project_id. Call this first when the user mentions a task by name and you don't have its integer ID — never invent task_id.

Filter tasks with Vikunja expression. Operators: = != > < >= <= in like. Logical: && ||. Time helpers: now, now/d, now+7d, now-3d. Fields: title, description, done, due_date, start_date, end_date, priority, project_id, percent_done.

Add a comment to a task (markdown supported).

Mention a user in a task comment. Vikunja auto-links '@username' and notifies. Use when user wants to notify/loop in someone.

List all comments on a task.

Edit the text of an existing comment on a task.

Permanently delete a comment from a task. Cannot be undone.

Delete MULTIPLE comments on a task at once. Pass comment_ids to delete specific ones, or omit comment_ids entirely to delete EVERY comment on the task. Pass task_id, or task_name (+ optional bucket_name to disambiguate) to resolve it by title. Use when the user asks to delete 2+ comments, or 'delete all comments on task X'.

Add MULTIPLE comments to a task at once, in order. Pass task_id, or task_name (+ optional bucket_name to disambiguate) to resolve it by title. Use when the user asks to post 2+ comments in one request, e.g. a simulated work log.

Break a task into subtasks using AI. Fetches the task title and description, generates N actionable subtask titles, then creates each as a real Vikunja subtask. Use when user says 'break this task into subtasks', 'разбей задачу', 'create a plan', or similar. Returns the list of created subtask IDs and titles.

Attach a file (photo, PDF, doc) to a task. Vikunja stores the file itself (max 20MB). Use when the user wants to attach/upload a photo or file to a task.

List all attachments (files/photos) on a task.

Remove a file attachment from a task. Cannot be undone.

Remove SEVERAL file attachments from a task at once. Pass task_id and attachment_ids (list of integers from list_task_attachments). Use when the user wants to remove 2+ attachments in one request. Cannot be undone.

Check whether live Vikunja notifications (assigned/commented) are enabled.

Turn on live notifications from your Vikunja — get notified in Imperal (bell/telegram, per your notification settings) when someone assigns you a task or comments on one. Registers a webhook on every one of your current Vikunja projects automatically — no manual setup needed. Projects created after enabling won't be covered until you disable and re-enable.

Turn off live Vikunja notifications and remove the webhooks from your Vikunja projects.