Home · Setup · Claude Code

MCP Onboarding in Claude Code

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.

`claude mcp add onboarding` at user scope is the level that matches the data: one store per machine holds the hires and the role templates, and applying a template stamps the version, so a template edited later never changes a hire who already copied it. There is no network call in the server, so it works identically offline.

What you get in Claude Code

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.

Install it in Claude Code

The file is .mcp.json, and the key inside it is mcpServers.

Scope	Path
local (default)	`~/.claude.json, this project only`
project	`.mcp.json at the repository root`
user	`~/.claude.json, every project`

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. Claude Code reads its own config, so here it is:

From the terminal, against a built file:

claude mcp add --scope user onboarding -- node /absolute/path/to/mcp-servers/servers/onboarding/dist/index.js
claude mcp list    # health-check it before the first prompt

# or --scope project, committed to .mcp.json for the team

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/onboarding

That 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:

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

No restart. The entry is picked up in the next session, and `/mcp` reconnects one on demand.

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.

No install: the hosted endpoint

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.

claude mcp add --transport http onboarding https://mcp.zovo.one/mcp/onboarding \
  --header "Authorization: Bearer <token>"

Claude Code notes worth knowing first

The `--` is load-bearing: it separates Claude Code's own options, such as --transport, --env and --scope, from the command that runs the server. And the default scope is local, private to you and to the directory you ran it in, so adding it in the wrong folder leaves the tools absent with no error at all.

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.

Questions

Which scope should I use for MCP Onboarding?

Local, the default, writes ~/.claude.json and is private to you and that directory. --scope project writes .mcp.json at the repository root, shared through version control. --scope user loads it everywhere.

Why did my first prompt ignore the server?

Measured, not documented: of three fresh projects, one first prompt made zero tool calls although initialize answered in 1.05 seconds. Run claude mcp list once first: it prints Connected, and the next run used the tool.

Can I use MCP Onboarding without installing anything?

Yes: claude mcp add --transport http onboarding https://mcp.zovo.one/mcp/onboarding --header "Authorization: Bearer <token>". Mint a free token at https://mcp.zovo.one/mcp/token or use a Pro key. -t and -H are the short forms.

MCP Onboarding in detail · The same server in Claude Desktop and Cursor · Every server in Claude Code · Guides · Claude Code docs · Buy Pro