Checkvist MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHECKVIST_API_KEY | Yes | Your Checkvist API key | |
| CHECKVIST_USERNAME | Yes | Your Checkvist email address |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| checkvist_list_checklistsA | Get all checklists for the authenticated user. Can filter for archived lists. |
| checkvist_get_checklistC | Get information about a specific checklist by ID |
| checkvist_create_checklistB | Create a new checklist |
| checkvist_update_checklistC | Update an existing checklist |
| checkvist_delete_checklistA | Delete a checklist (marks for deletion) |
| checkvist_get_tasksA | Get all tasks from a checklist as raw JSON. Use checkvist_get_tasks_summary instead for easier reading. Only use this when you need the complete JSON data structure. |
| checkvist_get_tasks_summaryA | Get tasks from a checklist in a readable text format (RECOMMENDED). For VERY LARGE checklists: use preview=true to see only top-level tasks. For large checklists: use compact=true to show all tasks with titles+IDs only. For small checklists: use default to see full details. |
| checkvist_get_taskA | Get a specific task by ID, including its parent hierarchy (returns JSON) |
| checkvist_get_task_treeA | Get a specific task and its subtasks in readable text format. Use max_depth to limit size if needed. |
| checkvist_get_checklist_statsA | Get statistics about a checklist: number of tasks, top-level tasks, average depth, etc. Use this first to understand checklist size. |
| checkvist_list_top_level_tasksA | Get ONLY the list of top-level task IDs and titles (no subtasks). Use this to get an overview, then use checkvist_get_task_tree to read each one individually. |
| checkvist_get_tasks_paginatedA | Get ALL tasks in chunks to avoid size limits. Returns a specific page of top-level tasks with their subtasks. Call multiple times with different page numbers to read entire checklist. |
| checkvist_create_taskB | Create a new task in a checklist |
| checkvist_update_taskC | Update an existing task |
| checkvist_close_taskC | Close/complete a task |
| checkvist_reopen_taskA | Reopen a closed task |
| checkvist_delete_taskA | Delete a task and its children |
| checkvist_invalidate_taskA | Mark a task as invalidated (status=2, different from closed) |
| checkvist_set_repeating_taskC | Configure a task to repeat on a schedule |
| checkvist_import_tasksA | Import multiple tasks at once in Checkvist format (indented text) |
| checkvist_get_notesA | Get all notes/comments for a task |
| checkvist_create_noteB | Create a note/comment on a task |
| checkvist_update_noteC | Update an existing note/comment |
| checkvist_delete_noteB | Delete a note/comment from a task |
| checkvist_get_current_userA | Get profile information for the authenticated user |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 25 tools
There are several overlapping task retrieval tools (get_tasks, get_tasks_summary, get_tasks_paginated, list_top_level_tasks, get_task, get_task_tree) that differ mainly in output format and verbosity. The descriptions help, but an agent could easily select the wrong one, especially for large checklists.
All 25 tools follow the consistent pattern checkvist_<verb>_<noun>, with clear verbs like get, list, create, update, delete, close, reopen. No mixed conventions or vague names.
25 tools is on the heavy side for a checklist app. Many retrieval variants (raw JSON, summary, paginated, top-level, task tree) could be consolidated into fewer tools, reducing cognitive load without losing functionality.
The tool surface covers CRUD for checklists, tasks, and notes, plus useful extras like stats, import, and repeating tasks. However, there is no explicit archive/restore checklist operation (despite filtering by archived) and no task reordering/moving, which are common in outliner apps.