# onboarding [Health: Active]

**Category:** 🏢 Workplace & Productivity  
**Repository:** https://github.com/theluckystrike/mcp-onboarding  
**GitHub Stars:** 0  
**npm Downloads (last month):** 474  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/onboarding

## Description
New-hire onboarding: task templates per role, day-one to day-ninety plans.

## Tools
Capabilities this server exposes over MCP:

- **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

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

## Documentation

## What the onboarding MCP server does

The onboarding MCP server organizes new-hire work around reusable checklists and dated runs. A checklist can represent a role or process, with a name, category, description, sections, and required steps. A run is created for a specific job or hire and records the actual answers, observations, people involved, and dates.

The system keeps checklist definitions separate from their runs. When a run starts, it receives a copy of the current checklist and records the source version. Later additions or removals affect new runs only. Deleting a checklist also leaves its existing runs readable because those runs contain their own step copies.

## How it works

Create a checklist, add its steps, and start a run when onboarding begins. Each step can be marked `pass`, `fail`, or `na`, with details about who checked it, when it was checked, and what was found. Counts, completion state, outstanding work, and sign-off eligibility are calculated from the run’s current steps rather than stored as fixed summary fields.

`na` is treated as answered but not passed. A run cannot normally be signed off when required work is unanswered or failed, when an optional step is unanswered, or when it has no steps. The `force` option permits sign-off with exceptions, which remain visible in the run and its report. Signed-off runs are frozen; complete runs can be reopened, and runs for work that did not happen can be abandoned.

## Setup and configuration

The server can run locally from source or through the hosted streamable-HTTP endpoint. For hosted use, obtain a token from the connection page or token endpoint, then send it as a bearer token to `https://mcp.zovo.one/mcp/onboarding`. Clients that cannot set headers can place the token in the URL path instead. Requests without a token receive an authorization error for tool calls.

For local use, clone the repository and run `npm install && npm run build`, then configure an MCP client to launch `dist/index.js` with Node. A downloadable `.mcpb` package is also available for Claude Desktop. The package is not currently published to npm, so an `npx` installation command is not a working setup path despite the example configurations in the documentation.

Local data is stored under `${XDG_DATA_HOME:-~/.local/share}/mcp-servers/checklist/`. The local server makes no network calls, uses no API key, and does not require an account. It reads a shared business profile only for the name and address shown on printed reports and does not write to that file.

## Tools and capabilities

Checklist tools create, update, inspect, list, and delete reusable templates. Run tools start dated runs, record step results, show details and blockers, filter run lists, sign off, reopen or abandon runs, delete runs, and produce text reports. Reports can be written to a `.txt` path on the Pro tier.

The free tier supports three retained checklists, unlimited runs, and up to 500 steps per checklist. Pro removes the retained-checklist limit and enables report file output; runs remain unlimited in both tiers. `license_status` reports the active tier, while `license_activate` stores a Pro key.

A `checklist://contract` resource documents the snapshot rule, item states, status transitions, sign-off conditions, and storage location. The `run_the_checklist` prompt guides an agent through a run in order.

## Limitations and notes

The onboarding MCP server does not provide a native npm package installation yet. A signed-off run cannot be deleted, and deleting a checklist does not delete its historical runs. Free usage is limited by the number of retained checklist definitions, not by the number of onboarding runs or steps per run.

_Full upstream README: https://allmcps.com/mcp/onboarding/readme_