Checkvist
for LuumenAI
Read and update Checkvist outlines, tasks, tags, and due dates from the terminal
Keep runbooks, migration checklists, and handover lists in Checkvist without leaving the terminal. Luumen reads a list as a markdown outline, follows a task and its subtasks, and searches by tag, due date, or state. Changes — new tasks, status updates, tag edits, bulk imports — are previewed and approved before they land. Connects with an API key.
The Checkvist toolbox
16 tools: 6 read, 10 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet ChecklistGet one Checkvist checklist's metadata by ID.
- ReadGet Tasks OutlineRead a checklist as a recommended markdown task outline, with controls for closed tasks, depth, compact output, or top-level preview.
- ReadGet Tasks PageRead one explicit 1-based page of a large Checkvist checklist.
- ReadGet Task TreeRead one Checkvist task and its subtasks as a markdown outline, optionally including closed items or notes and limiting depth.
- ReadList ChecklistsList checklists available to the authenticated Checkvist user, optionally including archived lists or omitting statistics for a faster response.
- ReadSearch TasksSearch tasks across the user's Checkvist checklists using words and operators for due date (^ or due:), tag (# or tag:), state (in:), and notes (has:note).
- WriteCreate ChecklistCreate a Checkvist checklist with a name and optional visibility and tags. Approval by default
- WriteCreate TaskCreate a task in a checklist, optionally under a parent and with tags, smart-syntax due date, position, priority, or assignees. Approval by default
- WriteDelete ChecklistMark a Checkvist checklist for deletion. Approval by default
- WriteDelete TaskPermanently delete a Checkvist task and all of its child tasks. Approval by default
- WriteImport TasksCreate multiple hierarchical tasks from Checkvist indented text. Approval by default
- WriteReplace TasksDelete every existing task in a checklist, then replace the hierarchy from Checkvist indented text or OPML. Approval by default
- WriteSet Task StatusSet a task's status to closed, reopened, or invalidated using Checkvist's dedicated status operations. Approval by default
- WriteUpdate ChecklistUpdate an existing checklist's name, visibility, or complete tag set. Approval by default
- WriteUpdate TaskUpdate task content, hierarchy, replacement tags, due date, position, priority, assignees, or smart-syntax parsing. Approval by default
- WriteUpdate Task TagsAdd and remove task tags without replacing the complete tag set. Approval by default
One prompt, start to finish
What a governed Checkvist run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create checklist, create task, delete checklist, delete task, and more — is shown as a plan and requires approval by default, including the 5 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Checkvist — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
Adobe Marketing Agent MCPAdobe Experience Platform context, sandbox switches, and async task status
AffindaRead parsed documents, collections, and annotations — change them with approval
Agent MailGive the agent its own mailbox for reading threads and sending updates
AI/ML APIInspect assistants, threads, and runs — and change them as approved stepsPut Checkvist to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.