Summary

This is the whole Quire object model rather than a task-adding shortcut, which makes it as usable for migration and reporting as for daily work — and equally usable for destroying a project.

Deletion is stated as irreversible on tasks, comments, documents, sublists, chat channels and stored values, and quire.deleteTask takes every subtask with it; nothing in the tool layer asks for confirmation first. The dual addressing helps once you hold OIDs and gets in the way before you do, so a session tends to start at quire.listProjects or a search and collect identifiers from there. Custom statuses are the feature worth planning around: they let the board match a real workflow, and deleting a status silently reverts its tasks to To-Do.

What it is

A Quire workspace client of 61 tools reaching organizations, projects, tasks, tags, custom statuses, comments, chat channels, documents, sublists, attachments and a key-value store.

What you get

Tasks addressable either way: quire.getTask and quire.updateTask accept a project ID plus task ID or a task OID alone, and quire.listTasks returns root-level tasks unless parentTaskOid asks for subtasks.
Position decided at creation: quire.createTask makes a root task or a subtask, while quire.createTaskAfter and quire.createTaskBefore place a task at the same level as a reference task.
Search that widens by scope: quire.searchTasks covers a project, quire.searchFolderTasks a folder, and quire.searchOrganizationTasks every project in an organization, each filtering on keyword, assigneeId, priority, status and tagId.
Workflow stages of your own: quire.createStatus, quire.updateStatus and quire.deleteStatus manage custom statuses beyond To-Do (0) and Complete (100), which are always available.
Export in a single call: quire.exportProject writes a project's tasks as JSON or CSV and reports progress when the client supplies a progressToken.
Discussion and evidence together: quire.addTaskComment and quire.addChatComment post to a task or a chat channel, pinned or not, and quire.uploadTaskAttachment and quire.uploadCommentAttachment attach a file by content, filename and mimeType.
A key-value store travelling with the workspace: quire.putStorageValue writes by name, quire.getStorageValue reads it back, and quire.listStorageEntries returns everything under a prefix.
Follower lists edited rather than replaced: quire.updateOrganization and quire.updateProject take addFollowers and removeFollowers as well as a complete followers set.

Requirements

A Quire account and an OAuth client registered against it — QUIRE_OAUTH_CLIENT_ID and QUIRE_OAUTH_CLIENT_SECRET. quire.whoami exists to confirm which account the session is connected as.

Setup effort

One command plus a key — npx -y quire-mcp, then supply credentials