io.github.theluckystrike/checklist

Official16 toolsLive

by theluckystrike · JavaScript

Reusable checklists and dated runs of them: pass, fail, not applicable, and a sign-off.

Model Context Protocol (MCP) Server: io.github.theluckystrike/checklist

This MCP server provides reusable checklists and dated runs of those checklists. The run items support outcomes including pass, fail, and not applicable, along with a sign-off field. The server description focuses on checklist reuse combined with tracking results over time.

🛠️ Key Features

Reusable checklists
Dated runs of checklists
Run statuses: pass, fail, not applicable
Sign-off associated with runs

🚀 Use Cases

Recording checklist executions with timestamps
Tracking whether checklist items were pass/fail/not applicable
Capturing sign-off for completed checklist runs

⚡ Developer Benefits

Standardized checklist structure for repeatable use
Simple status taxonomy for run results
Supports dated execution history

⚠️ Limitations

No additional capabilities (e.g., tool count, configuration, or integrations) are described in the provided data

Topics

claudecursorinvoicemcpmcp-servermodel-context-protocolspreadsheetaccountingai-toolsbookkeepingclaude-desktopfreelanceinvoicinglocal-firstmcp-serverspdfself-hostedtime-trackingvatproductivity

Captured live from the server via tools/list.

checklist_create

Create a reusable checklist and return its CL-NNNN id: a name, a category and an optional description. Add the steps with checklist_item_add. Free tier: 3 checklists, and unlimited runs of them.

Parameters3

name	string	required	What the checklist is, e.g. Pre-delivery vehicle check or Site handover
category	string	optional	A grouping key, lower-cased and hyphenated, e.g. handover or safety. Default general
description	string	optional	What this checklist is for and when to run it, printed at the top of a blank copy

Raw schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 200,
      "description": "What the checklist is, e.g. Pre-delivery vehicle check or Site handover"
    },
    "category": {
      "type": "string",
      "maxLength": 60,
      "description": "A grouping key, lower-cased and hyphenated, e.g. handover or safety. Default general"
    },
    "description": {
      "type": "string",
      "maxLength": 2000,
      "description": "What this checklist is for and when to run it, printed at the top of a blank copy"
    }
  },
  "required": [
    "name"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

checklist_item_add

Add one step to a checklist and return its I01-style id: the text, an optional section heading, and whether it is required. A required step that is unanswered or failed blocks sign-off; an optional one does not.

Parameters6

checklist	string	required	The checklist id, e.g. CL-0001, or its name when only one carries it
text	string	required	The step, as the person doing it will read it, e.g. Tyre pressures checked and recorded
section	string	optional	A heading to group this step under, e.g. Exterior. Steps keep the order they were added within a section
required	boolean	optional	Whether sign-off is blocked while this step is unanswered or failed. Default true
note	string	optional	Guidance printed under the step, e.g. the tolerance or the standard it is checked against
position	integer	optional	Insert at this 1-based position instead of at the end. Existing steps keep their ids

Raw schema

{
  "type": "object",
  "properties": {
    "checklist": {
      "type": "string",
      "maxLength": 200,
      "description": "The checklist id, e.g. CL-0001, or its name when only one carries it"
    },
    "text": {
      "type": "string",
      "maxLength": 2000,
      "description": "The step, as the person doing it will read it, e.g. Tyre pressures checked and recorded"
    },
    "section": {
      "type": "string",
      "maxLength": 60,
      "description": "A heading to group this step under, e.g. Exterior. Steps keep the order they were added within a section"
    },
    "required": {
      "type": "boolean",
      "description": "Whether sign-off is blocked while this step is unanswered or failed. Default true"
    },
    "note": {
      "type": "string",
      "maxLength": 2000,
      "description": "Guidance printed under the step, e.g. the tolerance or the standard it is checked against"
    },
    "position": {
      "type": "integer",
      "minimum": 1,
      "maximum": 500,
      "description": "Insert at this 1-based position instead of at the end. Existing steps keep their ids"
    }
  },
  "required": [
    "checklist",
    "text"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

checklist_item_remove

Remove one step from a checklist by its I01-style id and bump the checklist version. Runs already under way keep the step they started with, so nothing anybody already ticked is rewritten.

Parameters2

checklist	string	required	The checklist id, e.g. CL-0001, or its name when only one carries it
item	string	required	The step id, e.g. I03, as shown by checklist_show

Raw schema

{
  "type": "object",
  "properties": {
    "checklist": {
      "type": "string",
      "maxLength": 200,
      "description": "The checklist id, e.g. CL-0001, or its name when only one carries it"
    },
    "item": {
      "type": "string",
      "maxLength": 16,
      "description": "The step id, e.g. I03, as shown by checklist_show"
    }
  },
  "required": [
    "checklist",
    "item"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

checklist_show

One checklist with its steps in order, grouped by section, plus how many are required and how many runs have been started from it. Pass as_text for a blank printable copy with a box against each step.

Parameters2

checklist	string	required	The checklist id, e.g. CL-0001, or its name when only one carries it
as_text	boolean	optional	Return a blank printable copy as plain text as well as the structured view. Default false

Raw schema

{
  "type": "object",
  "properties": {
    "checklist": {
      "type": "string",
      "maxLength": 200,
      "description": "The checklist id, e.g. CL-0001, or its name when only one carries it"
    },
    "as_text": {
      "type": "boolean",
      "description": "Return a blank printable copy as plain text as well as the structured view. Default false"
    }
  },
  "required": [
    "checklist"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

checklist_list

Every checklist with its category, version, step count and how many runs came from it. Filter by category or by a word in the name. Returns at most 500 rows, newest change first.

Parameters2

category	string	optional	Only checklists in this category, matched after the same lower-case hyphenation applied on create
contains	string	optional	Only checklists whose name contains this text, matched case-insensitively

Raw schema

{
  "type": "object",
  "properties": {
    "category": {
      "type": "string",
      "maxLength": 60,
      "description": "Only checklists in this category, matched after the same lower-case hyphenation applied on create"
    },
    "contains": {
      "type": "string",
      "maxLength": 200,
      "description": "Only checklists whose name contains this text, matched case-insensitively"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

checklist_delete

Delete a checklist and its steps for good. Runs already started from it are untouched and stay readable: a run carries its own copy of the steps, so deleting the checklist does not erase what anybody signed.

Parameters2

checklist	string	required	The checklist id, e.g. CL-0001, or its name when only one carries it
confirm	boolean	required	Must be true. There is no undo and nothing is copied anywhere first

Raw schema

{
  "type": "object",
  "properties": {
    "checklist": {
      "type": "string",
      "maxLength": 200,
      "description": "The checklist id, e.g. CL-0001, or its name when only one carries it"
    },
    "confirm": {
      "type": "boolean",
      "const": true,
      "description": "Must be true. There is no undo and nothing is copied anywhere first"
    }
  },
  "required": [
    "checklist",
    "confirm"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

run_start

Start a dated run of a checklist and return its RUN-YYYY-NNNN id. The steps are COPIED into the run, so editing the checklist afterwards never changes a run already under way. Runs are free and never capped.

Parameters5

checklist	string	required	The checklist id, e.g. CL-0001, or its name when only one carries it
title	string	required	What this run is against, e.g. Van BX21 KLM, February service
reference	string	optional	The job, order or asset id this run belongs to, e.g. WO-2026-0044. Named only; no sibling store is opened
date	string	optional	The day the run happened, YYYY-MM-DD. Default today
note	string	optional

Raw schema

{
  "type": "object",
  "properties": {
    "checklist": {
      "type": "string",
      "maxLength": 200,
      "description": "The checklist id, e.g. CL-0001, or its name when only one carries it"
    },
    "title": {
      "type": "string",
      "maxLength": 200,
      "description": "What this run is against, e.g. Van BX21 KLM, February service"
    },
    "reference": {
      "type": "string",
      "maxLength": 64,
      "description": "The job, order or asset id this run belongs to, e.g. WO-2026-0044. Named only; no sibling store is opened"
    },
    "date": {
      "type": "string",
      "maxLength": 10,
      "description": "The day the run happened, YYYY-MM-DD. Default today"
    },
    "note": {
      "type": "string",
      "maxLength": 2000
    }
  },
  "required": [
    "checklist",
    "title"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

run_check

Mark one step pass, fail or na, with who did it and when. na means the step did not apply; it counts as answered and never as passed. A step can be answered again while the run is open, and the last answer stands.

Parameters6

run	string	required	The run id, e.g. RUN-2026-0001, or its title when only one carries it
item	string	required	The step id, e.g. I03, as shown by run_show
state	string	required	pass, fail, na for did not apply, or pending to put the step back to unanswered
by	string	optional	Who answered it. Printed against the step on the report
at	string	optional	The day it was answered, YYYY-MM-DD. Default the run's own date
note	string	optional	What was found. Say why on a fail: the report prints this under the step

Raw schema

{
  "type": "object",
  "properties": {
    "run": {
      "type": "string",
      "maxLength": 200,
      "description": "The run id, e.g. RUN-2026-0001, or its title when only one carries it"
    },
    "item": {
      "type": "string",
      "maxLength": 16,
      "description": "The step id, e.g. I03, as shown by run_show"
    },
    "state": {
      "type": "string",
      "enum": [
        "pending",
        "pass",
        "fail",
        "na"
      ],
      "description": "pass, fail, na for did not apply, or pending to put the step back to unanswered"
    },
    "by": {
      "type": "string",
      "maxLength": 200,
      "description": "Who answered it. Printed against the step on the report"
    },
    "at": {
      "type": "string",
      "maxLength": 10,
      "description": "The day it was answered, YYYY-MM-DD. Default the run's own date"
    },
    "note": {
      "type": "string",
      "maxLength": 2000,
      "description": "What was found. Say why on a fail: the report prints this under the step"
    }
  },
  "required": [
    "run",
    "item",
    "state"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

run_show

The whole run: every step with its answer, who answered it and when, grouped by section, plus the pass, fail and outstanding counts, the failures in full, and whether it can be signed off and why not.

Parameters1

run

string

required

The run id, e.g. RUN-2026-0001, or its title when only one carries it

Raw schema

{
  "type": "object",
  "properties": {
    "run": {
      "type": "string",
      "maxLength": 200,
      "description": "The run id, e.g. RUN-2026-0001, or its title when only one carries it"
    }
  },
  "required": [
    "run"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

run_list

Runs newest first, with their checklist, progress and sign-off state. Filter by checklist, by status, by reference or to open runs only. Returns at most 500 rows.

Parameters5

checklist	string	optional	Only runs of this checklist, by id or name
status	string	optional	Only runs in this status
open_only	boolean	optional	Only open and complete runs, the ones still editable. Default false
reference	string	optional	Only runs against this job, order or asset id, matched case-insensitively
with_failures	boolean	optional	Only runs that have at least one failed step. Default false

Raw schema

{
  "type": "object",
  "properties": {
    "checklist": {
      "type": "string",
      "maxLength": 200,
      "description": "Only runs of this checklist, by id or name"
    },
    "status": {
      "type": "string",
      "enum": [
        "open",
        "complete",
        "signed_off",
        "abandoned"
      ],
      "description": "Only runs in this status"
    },
    "open_only": {
      "type": "boolean",
      "description": "Only open and complete runs, the ones still editable. Default false"
    },
    "reference": {
      "type": "string",
      "maxLength": 64,
      "description": "Only runs against this job, order or asset id, matched case-insensitively"
    },
    "with_failures": {
      "type": "boolean",
      "description": "Only runs that have at least one failed step. Default false"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

run_sign_off

Sign off a completed run with a name and a date, which freezes it. Refused while a required step is unanswered or failed, unless force is true, and either way the exceptions stay on the record and print on the report.

Parameters5

run	string	required	The run id, e.g. RUN-2026-0001, or its title when only one carries it
by	string	required	Who is signing it off, as it should read on the document
date	string	optional	The day it was signed, YYYY-MM-DD. Default today
note	string	optional	What the signature covers, or the exception being accepted
force	boolean	optional	Sign off even though required steps are unanswered or failed. Default false; the reasons come back either way

Raw schema

{
  "type": "object",
  "properties": {
    "run": {
      "type": "string",
      "maxLength": 200,
      "description": "The run id, e.g. RUN-2026-0001, or its title when only one carries it"
    },
    "by": {
      "type": "string",
      "maxLength": 200,
      "description": "Who is signing it off, as it should read on the document"
    },
    "date": {
      "type": "string",
      "maxLength": 10,
      "description": "The day it was signed, YYYY-MM-DD. Default today"
    },
    "note": {
      "type": "string",
      "maxLength": 2000,
      "description": "What the signature covers, or the exception being accepted"
    },
    "force": {
      "type": "boolean",
      "description": "Sign off even though required steps are unanswered or failed. Default false; the reasons come back either way"
    }
  },
  "required": [
    "run",
    "by"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

run_status

Move a run back to open so a step can be answered again, or abandon it when the job did not happen. A signed-off run is refused: a signature is the point at which a run stops moving.

Parameters4

run	string	required	The run id, e.g. RUN-2026-0001, or its title when only one carries it
status	string	required	open puts a complete run back into edit; abandoned closes it without a signature
date	string	optional	The day the step happened, YYYY-MM-DD. Default today
note	string	optional	Why. Kept on the run's history and printed nowhere else

Raw schema

{
  "type": "object",
  "properties": {
    "run": {
      "type": "string",
      "maxLength": 200,
      "description": "The run id, e.g. RUN-2026-0001, or its title when only one carries it"
    },
    "status": {
      "type": "string",
      "enum": [
        "open",
        "abandoned"
      ],
      "description": "open puts a complete run back into edit; abandoned closes it without a signature"
    },
    "date": {
      "type": "string",
      "maxLength": 10,
      "description": "The day the step happened, YYYY-MM-DD. Default today"
    },
    "note": {
      "type": "string",
      "maxLength": 2000,
      "description": "Why. Kept on the run's history and printed nowhere else"
    }
  },
  "required": [
    "run",
    "status"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

run_report

The run as plain text on every tier: every step with its mark, who answered it, the notes, the counts and a signature block or the recorded signature. Pro also gets it back as a .txt download link valid for one hour, named by out_path.

Parameters3

run	string	required	The run id, e.g. RUN-2026-0001, or its title when only one carries it
out_path	string	optional	Name for the downloaded .txt file, e.g. site-handover-run. Pro only. Omit to get the report back as text, which every tier can do; the file comes back as a download link valid for one hour
overwrite	boolean	optional	Replace out_path if a file is already there. Default false, and an existing file is refused with nothing written

Raw schema

{
  "type": "object",
  "properties": {
    "run": {
      "type": "string",
      "maxLength": 200,
      "description": "The run id, e.g. RUN-2026-0001, or its title when only one carries it"
    },
    "out_path": {
      "type": "string",
      "maxLength": 1000,
      "description": "Name for the downloaded .txt file, e.g. site-handover-run. Pro only. Omit to get the report back as text, which every tier can do; the file comes back as a download link valid for one hour"
    },
    "overwrite": {
      "type": "boolean",
      "description": "Replace out_path if a file is already there. Default false, and an existing file is refused with nothing written"
    }
  },
  "required": [
    "run"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

run_delete

Delete a run for good, with every answer on it. A signed-off run is refused: it is the record of what somebody put their name to. Abandon a run you no longer want instead of deleting a signed one.

Parameters2

run	string	required	The run id, e.g. RUN-2026-0001, or its title when only one carries it
confirm	boolean	required	Must be true. There is no undo and nothing is copied anywhere first

Raw schema

{
  "type": "object",
  "properties": {
    "run": {
      "type": "string",
      "maxLength": 200,
      "description": "The run id, e.g. RUN-2026-0001, or its title when only one carries it"
    },
    "confirm": {
      "type": "boolean",
      "const": true,
      "description": "Must be true. There is no undo and nothing is copied anywhere first"
    }
  },
  "required": [
    "run",
    "confirm"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

license_status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}

license_activate

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Parameters1

key

string

required

License key from checkout, MCPL1.<payload>.<signature>

Raw schema

{
  "type": "object",
  "properties": {
    "key": {
      "type": "string",
      "description": "License key from checkout, MCPL1.<payload>.<signature>"
    }
  },
  "required": [
    "key"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

servers/checklist/README.md6 KBView on GitHub

mcp-checklist

In the official MCP Registry (io.github.theluckystrike/checklist). Checklists you build once and run many times, and the dated record of each run that somebody signs. A checklist is a named list of steps, optionally grouped into sections, each one required or optional. A run is one pass of that checklist against a job: every step is marked pass, fail or not applicable, with who marked it and on what day, and a note that says what was found. run_sign_off then puts a name and a date on it and freezes it.

The one rule that decides everything else

If somebody edits the checklist afterwards, adds a step or deletes one, every run already in progress keeps the list it started with, and the version it was copied from is recorded on the run.

That is not a caching convenience. A checklist somebody ticked and signed has to be the list they actually saw. A run that read its steps live from the checklist would mean a signed handover certificate for eleven checks when the person signing it saw ten, with no field in the record showing that it had happened. It also means deleting a checklist leaves its runs readable and complete, which is what you want the year afterwards when somebody asks what was checked.

Two smaller rules follow from it:

Nothing derived is stored. The pass, fail and outstanding counts, the percentage, and whether a run can be signed off are worked out on every call from the run's own steps. A stored "complete" flag is a fact about the afternoon somebody last looked, and complete here is a reading: it appears when the last step is answered and goes away again when one is put back to pending.
Not applicable is not a pass. na counts as ANSWERED and never as passed. A step that was looked at and dismissed is a different fact from a step that passed, and merging the two is how a checklist reports full marks for a job where half the steps did not apply.

What blocks a signature

A required step that is unanswered, a required step that failed, an unanswered optional step, or a run with no steps. force: true signs anyway, and the exceptions stay on the record and print on the report under "Signed with exceptions". They are not lost, and they are not silent.

Install

One-click (.mcpb): download checklist.mcpb from the latest release and double-click it in Claude Desktop: https://github.com/theluckystrike/mcp-servers/releases/latest

npm publish for @theluckystrike/mcp-checklist is pending, so the npx line below returns 404 today. Build from source in the meantime; see llms-install.md.

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

json

{
  "mcpServers": {
    "checklist": {
      "command": "npx",
      "args": ["-y", "@theluckystrike/mcp-checklist"]
    }
  }
}

Claude Code

claude mcp add checklist -- npx -y @theluckystrike/mcp-checklist

Cursor

~/.cursor/mcp.json (global) or .cursor/mcp.json (project), same entry as Claude Desktop.

Tools

Tool	What it does
`checklist_create`	Create a reusable checklist: a name, a category, a description
`checklist_item_add`	Add a step: the text, a section heading, and whether it is required
`checklist_item_remove`	Remove a step and bump the version. Runs already under way keep it
`checklist_show`	One checklist, grouped by section, with a blank printable copy on request
`checklist_list`	Every checklist with its version, step count and how many runs came from it
`checklist_delete`	Delete a checklist. Its runs stay readable, because each carries its own copy
`run_start`	Start a dated run against a job. The steps are copied into it at this point
`run_check`	Mark one step pass, fail or na, with who and when and what was found
`run_show`	The run: every step with its answer, the counts, the failures, and what blocks sign-off
`run_list`	Runs newest first, filtered by checklist, status, reference, or only those with failures
`run_sign_off`	Sign off with a name and a date, which freezes the run
`run_status`	Reopen a complete run, or abandon one when the job did not happen
`run_report`	The run as text on every tier. Pro also writes it to `out_path` as a .txt file
`run_delete`	Delete a run. A signed-off one is refused
`license_status`	Which tier this install is on and where the key came from
`license_activate`	Store a Pro key for this server

There is also a resource, checklist://contract, carrying the snapshot rule, the item states, the run status machine, what blocks a sign-off and where this server writes; and a prompt, run_the_checklist, that walks the whole job in order.

Free vs Pro

	Free	Pro
Checklists you keep	3	unlimited
Runs of them	unlimited	unlimited
Steps per checklist	up to 500	up to 500
`run_show`, `run_list`, the counts	yes	yes
The run report as text	yes	yes
Writing the report to a file with `out_path`	no	yes

The meter is on how many DIFFERENT checklists you keep, not on how many jobs you check. A trade with one pre-delivery check, one handover sheet and one snag list runs its whole year inside the free tier. Runs are never capped, because capping the running of a checklist would cap the only thing a checklist is for. Deleting a checklist frees a slot.

Get Pro: https://mcp.zovo.one/buy/checklist (one-time), or all servers for one price at https://mcp.zovo.one/buy/bundle

Privacy

All data stays local, in ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/checklist/. There is no network call anywhere in this server, no API key, and no account. The only file it reads that it does not own is the shared business profile, for the name and address at the top of a printed report, and it never writes to it.

Built by theluckystrike. Support: support@zovo.one

Use these docs as an MCP server

Any MCP client (Claude, Cursor, Windsurf, VS Code) can read this repository's documentation directly via GitMCP - no install:

Docs MCP URL: https://gitmcp.io/theluckystrike/mcp-checklist

Install

Tools (16)

checklist_createchecklist_item_addchecklist_item_removechecklist_showchecklist_listchecklist_deleterun_startrun_check

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://mcp.zovo.one/mcp/checklist

Configuration

Environment variables

MCP_LICENSE_KEYsecret

Optional Pro license key (MCPL1....). Verified offline.

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "checklist": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.zovo.one/mcp/checklist"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

Model Context Protocol (MCP) Server: io.github.theluckystrike/checklist

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

checklist_create

checklist_item_add

checklist_item_remove

checklist_show

checklist_list

checklist_delete

run_start

run_check

run_show

run_list

run_sign_off

run_status

run_report

run_delete

license_status

license_activate

mcp-checklist

The one rule that decides everything else

What blocks a signature

Install

Claude Desktop

Claude Code

Cursor

Tools

Free vs Pro

Privacy

Use these docs as an MCP server

Install

Remote endpoint

Configuration

Related servers