Home · Setup · Claude.ai and Claude Desktop connectors
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.
The hires and the role templates live in the hosted store behind the token, so a plan applied here stamps the template version once, and a template edited later never changes a hire who already copied it. There is no network call inside the server on any route, so progress and overdue read exactly the same here as on a laptop, and nothing the connector holds is ever written to a local disk.
| 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.
https://mcp.zovo.one/mcp/connect mints an anonymous token and prints a URL per server, including this one, shaped like https://mcp.zovo.one/mcp/onboarding/t/<token>. That URL works with no headers: the token is in the path, not in an Authorization field this form does not have.
Idle anonymous tokens are swept after 30 days. Since this route has no filesystem, a file MCP Onboarding generates comes back as a download link that expires after one hour. A Pro key can replace the token in the same URL and removes the free-tier limits.
On an individual Pro or Max plan you add the connector yourself from Customize, Connectors. On Team and Enterprise it is the other way round: only an Owner or Primary Owner can add a custom connector, at Organization settings, Connectors, and members then connect to what the Owner added rather than pasting their own URL.
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, and binds to the token after checkout.
No. Add custom connector offers an Advanced settings section with an OAuth Client ID and Client Secret, but the connect-by-URL route does not use it. Leave both blank: the token in the URL path is what authenticates.
That is documented, not a bug: on Team and Enterprise, only an Owner or Primary Owner can add a custom connector, at Organization settings, Connectors, Add, Custom, Web. After that, members connect to the URL the Owner added from Customize, Connectors.
Yes. The token segment of the URL from /mcp/connect can be replaced with a Pro key, which removes the free-tier limits on MCP Onboarding for that connector.
The connector runs server-side with no filesystem of its own, so any file MCP Onboarding produces is handed back as a download link that expires after one hour, rather than a path on disk.
MCP Onboarding in detail · How connect-by-URL works · Every server for Claude.ai and Claude Desktop connectors · All clients · Claude.ai and Claude Desktop connectors docs · Buy Pro