New-hire onboarding plans: one hire at a time or a whole cohort from a role template. You add a hire (name, role, start day), build their task plan with owners (hr, manager or it) and due dates counted from the start, or apply a role template once and let every hire in that role inherit it with the template's version recorded. Mark tasks done or skipped as they happen (skipped is a deliberate dismissal that never counts as done), watch percent complete and overdue per hire, and onboarding_overdue lists everything still outstanding past its due date, most overdue first. Editing a template after applying it never changes a hire who already copied it.
In agent mode the overdue ordering must come from the server: onboarding_overdue lists everything past its due date, most overdue first, with owners and due dates counted from the start day, so an agent ranking tasks by hand is composing an estimate the server already gives exactly.
| You say | Tool |
|---|---|
| Ada Lovelace starts Monday as analytics-engineer; set her up. | onboarding_hire_add |
| Apply the analytics-engineer template to her plan. | onboarding_template_apply |
| What is still outstanding for Ada, and anything overdue across the team? | onboarding_progress then onboarding_overdue |
The unit suite is 18 tests, 18 passing, 0 failing (node --test, node v22), covering the template copy and version stamp, the done/skipped split and the overdue ordering; adversarial, concurrency and contract suites sit alongside it.
The file is .vscode/mcp.json, and the key inside it is servers.
| Scope | Path |
|---|---|
| This workspace | <workspace>/.vscode/mcp.json |
| Every workspace | the user profile mcp.json, opened by the MCP: Open User Configuration command |
If you also run Claude Desktop, the shortest path there is one click: onboarding.mcpb
from the latest release opens as an extension, with no JSON and no terminal.
VS Code reads its own config, so here it is:
// .vscode/mcp.json (the key is "servers")
{
"servers": {
"onboarding": {
"command": "node",
"args": ["/absolute/path/to/mcp-servers/servers/onboarding/dist/index.js"]
}
}
}Or from a terminal:
code --add-mcp '{"name":"onboarding","command":"node","args":["/absolute/path/to/mcp-servers/servers/onboarding/dist/index.js"]}'The node command above wants a built file. From a clone, once:
git clone https://github.com/theluckystrike/mcp-servers.git
cd mcp-servers && npm install
npm run build -w packages/mcp-license -w servers/onboardingThat writes servers/onboarding/dist/index.js, and its absolute path is the one argument
the config needs.
The npm packages are not published yet, so the form below returns a 404 today. It is here because it is what the entry becomes the day the publish lands, with nothing else changed:
code --add-mcp '{"name":"onboarding","command":"npx","args":["-y","@theluckystrike/mcp-onboarding"]}'VS Code asks you to confirm you trust the server and its capabilities before it starts. Nothing runs until you answer.
Nothing is published to npm yet, so the working install paths are the ones above: the .mcpb bundle from the latest release, a clone and build, or the hosted URL.
The same server runs at https://mcp.zovo.one/mcp/onboarding over MCP streamable HTTP, no install. Mint a free token with curl https://mcp.zovo.one/mcp/token, or use a Pro key. It has no filesystem, so a file comes back as a one-hour download link.
{
"servers": {
"onboarding": {
"url": "https://mcp.zovo.one/mcp/onboarding",
"headers": { "Authorization": "Bearer <token>" }
}
}
}The top-level key is "servers", not "mcpServers". A config pasted from a Claude Desktop or Cursor README parses cleanly, contributes no servers, and gives you no error to read, which makes it the most expensive one-word mistake here. Alongside it an "inputs" array holds secrets. The newer Agent Host reads a workspace .mcp.json instead.
Free: Every tool is free for one hire at a time: add, list, tasks, done, one-hire template apply, progress and overdue. Up to 500 rows on every list on every tier. Pro is $19 once, verified offline.
The key is servers, not mcpServers. A config copied from a Claude Desktop README parses cleanly and contributes nothing. Rename it. On the newer Agent Host, use a workspace .mcp.json instead.
No. code --add-mcp takes the server object on the command line, and MCP: Add Server in the palette asks whether the target is Workspace or Global.
In Chat, behind the tools picker, once the server has started. Adding or changing one raises a prompt asking you to confirm you trust it; if the picker is empty, that prompt is usually still waiting.
MCP Onboarding in detail · The same server in Cursor and Windsurf · Every server in VS Code · Guides · VS Code docs · Buy Pro