Checkvist
Checkvist beta PRO MCP lets AI assistants manage hierarchical lists, tasks, tags, due dates, and assignees, and read task notes.
Verdict
Common use cases
- Turn meeting notes into actionable task trees
- Draft sprint backlogs with nested subtasks
- Archive completed project checklists automatically
- Assign tasks to teammates during planning
- Pull checklist status into standup summaries
Integration
- Vendor
- Checkvist
- Category
- other
- Auth
- API_KEY
- Tools
- 16
- Composio slug
checkvist
Tools
- Create Checklist
Create a Checkvist checklist with a name and optional visibility and tags.
- Create Task
Create a task in a checklist, optionally under a parent and with tags, smart-syntax due date, position, priority, or assignees.
- Delete Checklistdestructive
Mark a Checkvist checklist for deletion. This destructive operation affects the checklist and all data it contains.
- Delete Taskdestructive
Permanently delete a Checkvist task and all of its child tasks. This is a destructive operation and cannot be undone with this tool.
- Get Checklist
Get one Checkvist checklist's metadata by ID. Use Get Tasks Outline to read the checklist's tasks.
- Get Tasks Outline
Read a checklist as a recommended markdown task outline, with controls for closed tasks, depth, compact output, or top-level preview. Checkvist requires a PRO account or active PRO trial for MCP tool execution.
- Get Tasks Page
Read one explicit 1-based page of a large Checkvist checklist. Each page contains one top-level task and its subtree. Call again with another page number to continue; Checkvist does not provide a verified continuation signal.
- Get Task Tree
Read one Checkvist task and its subtasks as a markdown outline, optionally including closed items or notes and limiting depth. Checkvist requires a PRO account or active PRO trial for MCP tool execution.
- Import Tasks
Create multiple hierarchical tasks from Checkvist indented text. Large imports can take at least a minute and must not be retried early because a retry can duplicate tasks. This tool preserves existing tasks; use Replace Tasks to delete and
- List Checklists
List checklists available to the authenticated Checkvist user, optionally including archived lists or omitting statistics for a faster response. Checkvist requires a PRO account or active PRO trial for MCP tool execution.
- Replace Tasks
Delete every existing task in a checklist, then replace the hierarchy from Checkvist indented text or OPML. OPML can also replace the checklist name and tags. Large replacements can take at least a minute and must not be retried early becau
- Search Tasks
Search 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). Returns one explicit 1-based page of up to 50 matches.
- Set Task Status
Set a task's status to closed, reopened, or invalidated using Checkvist's dedicated status operations.
- Update Checklist
Update an existing checklist's name, visibility, or complete tag set. At least one update field is required. An empty tags string removes all checklist tags.
- Update Task
Update task content, hierarchy, replacement tags, due date, position, priority, assignees, or smart-syntax parsing. At least one update field is required. Use Set Task Status for completion state.
- Update Task Tags
Add and remove task tags without replacing the complete tag set. Tag values are plain words without '#'. At least one of add or remove must be non-empty.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the MCP integrations page. 2. Click 'Add Integration' and select Checkvist from the list. 3. Open Checkvist in a browser, sign in, and go to Settings → API to generate a new API key. 4. Copy the key and paste it into the Switchy connection form, then click 'Connect'. 5. Switchy will verify the key and confirm the connection. 6. Open any Project in your workspace and type '@Checkvist' in the chat to see available tools. 7. Test the connection by asking '@Checkvist list my checklists' or '@Checkvist create a checklist named Test'. 8. If you see a response with checklist data or a confirmation, the integration is live.
What teammates see: by default, memories from Checkvist are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Create Sprint Backlog
@Checkvist create a checklist named 'Q2 Sprint 3' with three tasks: 'User onboarding flow', 'Payment integration', and 'Dashboard redesign'. Make each task a parent with two placeholder subtasks.
Read Roadmap Outline
@Checkvist get the tasks outline for checklist ID 12345 as markdown, including closed tasks and limiting depth to 3 levels.
Assign Tasks in Bulk
@Checkvist in checklist 67890, create three tasks under parent task 'Launch prep': 'Write release notes' assigned to Alice, 'Update docs' assigned to Bob, and 'QA smoke test' assigned to Carol.
Archive Completed Project
@Checkvist delete the checklist with ID 11223 named 'Old Campaign Tasks' — it's complete and no longer needed.
Triage Task Tree
@Checkvist get the task tree for task ID 98765 in checklist 54321, including all subtasks and notes, limited to 2 levels deep.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@checkvist summarize what's blocking our launch based on all high-priority overdue tasks across my checklists
Analyzing your Checkvist account, I found 4 high-priority overdue tasks that may block launch: In 'Q1 Launch' checklist: 'Finalize pricing page copy' (3 days overdue, assigned to Mike), 'Legal review of ToS' (1 day overdue, unassigned). In 'Marketing Assets' checklist: 'Export final logo files' (5 days overdue, assigned to Design team), 'Set up analytics tracking' (2 days overdue, assigned to you). The pricing copy and legal review appear to be on the critical path for launch readiness.
This synthesis example combines Get Tasks Outline across multiple checklists with AI reasoning to identify blockers. The MCP provides structured task data (priority, due dates, assignees) that the AI filters and interprets. Requires PRO account. The AI's 'blocking' assessment is inferential, not derived from explicit dependency data in Checkvist.
Use-case deep-dives
When nested task outlines beat flat project boards
A 6-person engineering team runs weekly retros and needs to track action items that spawn sub-tasks as blockers surface. Checkvist's Get Tasks Outline and Create Task tools let the AI read the full retro checklist as markdown, propose new tasks under the right parent, and update priorities without switching apps. The 16-tool scope means the AI can create, read, update, and delete tasks in one conversation thread. The catch: Checkvist requires a PRO account for the outline tools, so if your team is on the free tier, you'll hit auth errors mid-conversation. If you're already paying for PRO and your retros generate 20+ nested action items per sprint, this MCP keeps the AI in sync with your actual task tree. Book a call if you need the AI to own retro follow-through without manual copy-paste.
How this MCP handles repeatable multi-step workflows
A 3-person agency onboards 4-6 clients per month, each following a 40-step checklist with conditional branches (if enterprise, add security review; if startup, skip legal). The AI uses Create Checklist to clone the template, then Create Task to add client-specific steps and assignees based on intake form data. The smart-syntax due date parser means the AI can say 'next Friday' and Checkvist translates it. The Delete Task tool is destructive and permanent, so the AI should confirm before removing steps. This works when your onboarding is checklist-shaped and you trust the AI to write tasks in your house style. If your process lives in a CRM or needs audit trails, a project-management MCP is safer. If you run 5+ onboardings a month and spend an hour per checklist setup, this MCP pays for itself in week one.
When this MCP fits solo knowledge work
A solo consultant researches 3-4 topics per quarter and uses Checkvist to outline findings, with each top-level task as a research question and subtasks as sources or quotes. The AI reads the outline with Get Tasks Outline, suggests new subtasks under the right question, and marks tasks closed when the research is done. The Get Task Tree tool limits depth, so the AI can focus on one branch without loading the entire 200-task checklist. The trade-off: Checkvist's markdown export is read-only in the MCP, so if you need the AI to rewrite prose notes or generate reports, you'll copy-paste. This MCP wins when your research is task-shaped (questions, sources, next steps) rather than document-shaped (essays, slide decks). If you're already a Checkvist power user and want the AI to maintain your outlines, set up API key auth and start with one checklist.
Frequently asked
What does the Checkvist MCP do in Switchy?
It connects your Checkvist account so AI agents can read and write your checklists and tasks. Agents can create new checklists, add tasks with due dates and priorities, nest subtasks, and pull entire outlines into markdown format. Useful when you want AI to draft project plans, parse meeting notes into action items, or query your existing task hierarchy without leaving the chat.
Do I need a Checkvist PRO account to use this MCP?
Yes, for the most useful tools. Reading task outlines and task trees requires an active Checkvist PRO subscription or trial. Basic operations like creating checklists and tasks work on the free tier, but you won't be able to pull existing data into Switchy without PRO. Generate an API key from your Checkvist settings page to authenticate.
Can the MCP move tasks between checklists or reorder them?
The current tool set doesn't expose move or reorder operations. You can create a task at a specific position within a checklist and nest it under a parent, but bulk reorganisation or cross-checklist transfers aren't supported. If you need to restructure, you'll still do that in the Checkvist web UI or mobile app.
Why use this instead of just opening Checkvist in a browser tab?
The MCP lets AI read your task context and write back without you copy-pasting. An agent can scan your current sprint checklist, draft three new subtasks based on a Slack thread, and insert them under the right parent—all in one prompt. You stay in Switchy; the agent handles the Checkvist API calls and markdown formatting.
Who on the team should connect the Checkvist MCP?
Whoever owns the master task lists you want AI to access. The API key grants full read-write access to that user's checklists, including destructive operations like deleting tasks. If your team shares one Checkvist account, connect it once. If everyone has separate accounts, each person connects their own key to query their own lists.