Koskamo

theluckystrike MCP Onboarding

Manages new-hire onboarding using role-based task templates. It allows users to add hires, apply templates with owners and due dates, track progress, and identify overdue tasks. The server supports both hosted access via a free token and local installation via npm or a bundle file.

Visit theluckystrike

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

theluckystrike MCP Onboarding logo, by theluckystrikeCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-06Published by theluckystrike
MCP endpoint (Streamable HTTP)
https://mcp.zovo.one/mcp/onboarding
Vendor documentation

What its tools do

9 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Read-only (2)

Can change data (7)

9 of 9 have a description · 9 of 9 declare behavior hints · 8 of 8 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Plan a developer's first month with role-based tasks
  • List every late onboarding task with owner and days late
  • Apply a template to multiple hires in one call
  • Mark a specific onboarding task as done

Source and maintenance

Community listingRegistry 0.23.0
mcp-registry: io.github.theluckystrike/onboarding@0.23.0Source repositoryProject website
Maintenance checked

Protocol and capabilities

Server
mcp-onboarding 0.22.6
MCP protocol negotiated in check
2025-11-25
Tools
9 advertised
Resources
2 advertised
Resource templates
0 advertised
Prompts
2 advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  },
  "prompts": {
    "listChanged": true
  },
  "resources": {
    "listChanged": true
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

New hire onboarding plans. It covers hires with role and start date, tasks owned by HR, the manager or IT with due dates counted from the start date, role templates copied into each hire's plan, tasks done or skipped, each hire's progress, and tasks past their due date across all hires. Records are stored per user account on McpStamp's hosted service. A template applies to one hire on the free tier; applying it to many hires and CSV export need Pro. One lifetime key unlocks this server and all 58 others: https://mcp.zovo.one/buy/bundle?src=instr.onboarding

Tools

9 advertised

onboarding_hire_add — Add a hire
Advertised by the server during the last successful anonymous check.

Add a new hire and return its H-NNNN id: a name, a role and the day they start. The role is a grouping key, lower-cased and hyphenated. Add tasks with onboarding_task_add, or apply a role template with onboarding_template_apply.

onboarding_hire_add input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "name",
    "role",
    "start_date"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 200,
      "description": "The hire's name, e.g. Ada Lovelace"
    },
    "role": {
      "type": "string",
      "maxLength": 60,
      "description": "The role, e.g. engineer or sales. Lower-cased and hyphenated"
    },
    "start_date": {
      "type": "string",
      "maxLength": 10,
      "description": "The day they start, YYYY-MM-DD. Task due dates are counted from here"
    }
  }
}
onboarding_hire_add annotations
{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}
onboarding_hire_list — List hires
Advertised by the server during the last successful anonymous check.

Every hire with their role, start date, task counts, percent complete and overdue count. Filter by role or by a word in the name. Returns at most 500 rows, newest change first.

onboarding_hire_list input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "role": {
      "type": "string",
      "maxLength": 60,
      "description": "Only hires in this role, matched after the same lower-case hyphenation applied on add"
    },
    "contains": {
      "type": "string",
      "maxLength": 200,
      "description": "Only hires whose name contains this text, matched case-insensitively"
    }
  }
}
onboarding_hire_list annotations
{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}
onboarding_task_add — Add a task to a hire
Advertised by the server during the last successful anonymous check.

Add one task to a hire's plan and return its K01-style id: the text, who owns it (hr, manager or it) and how many days after the start date it is due. The due date is counted from the hire's start date.

onboarding_task_add input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "hire",
    "text",
    "owner",
    "due_offset"
  ],
  "properties": {
    "hire": {
      "type": "string",
      "maxLength": 200,
      "description": "The hire id, e.g. H-0001, or the name when only one carries it"
    },
    "text": {
      "type": "string",
      "maxLength": 2000,
      "description": "The task, as the person doing it will read it, e.g. Issue laptop and security badge"
    },
    "owner": {
      "enum": [
        "hr",
        "manager",
        "it"
      ],
      "type": "string",
      "description": "Who owns the task: hr, manager or it"
    },
    "due_offset": {
      "type": "integer",
      "maximum": 365,
      "minimum": 0,
      "description": "Days after the hire's start date the task is due. 0 is day one"
    }
  }
}
onboarding_task_add annotations
{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}
onboarding_task_done — Mark a task done or skipped
Advertised by the server during the last successful anonymous check.

Mark one task on a hire done or skipped, with the day it happened. done counts toward the percent complete; skipped is a deliberate dismissal and never counts as done. A task can be set back to todo to reopen it.

onboarding_task_done input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "hire",
    "task",
    "status"
  ],
  "properties": {
    "date": {
      "type": "string",
      "maxLength": 10,
      "description": "The day it was completed, YYYY-MM-DD. Default today"
    },
    "hire": {
      "type": "string",
      "maxLength": 200,
      "description": "The hire id, e.g. H-0001, or the name when only one carries it"
    },
    "task": {
      "type": "string",
      "maxLength": 16,
      "description": "The task id, e.g. K03, as shown by onboarding_progress"
    },
    "status": {
      "enum": [
        "todo",
        "done",
        "skipped"
      ],
      "type": "string",
      "description": "done, skipped, or todo to put it back to outstanding"
    }
  }
}
onboarding_task_done annotations
{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}
onboarding_template_apply — Apply a role template to a hire
Advertised by the server during the last successful anonymous check.

Apply a role template to one hire (free) or many (Pro), copying the template's tasks into each hire with the template's version recorded. Editing the template afterwards never changes a hire already under way. If no template exists for the role, one is created from the tasks you pass.

onboarding_template_apply input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "hire"
  ],
  "properties": {
    "hire": {
      "type": "string",
      "maxLength": 200,
      "description": "The hire to apply the template to. Pro: pass a comma-separated list of hire ids or names to apply to many at once"
    },
    "role": {
      "type": "string",
      "maxLength": 60,
      "description": "The role template to apply, by id (T-0001) or role. If omitted, the hire's own role is used"
    },
    "tasks": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "text"
        ],
        "properties": {
          "text": {
            "type": "string",
            "maxLength": 2000
          },
          "owner": {
            "enum": [
              "hr",
              "manager",
              "it"
            ],
            "type": "string",
            "default": "manager"
          },
          "due_offset": {
            "type": "integer",
            "default": 0,
            "maximum": 365,
            "minimum": 0
          }
        }
      },
      "maxItems": 500,
      "description": "When no template exists for the role, create one from these tasks and apply it. Pro only when applying to more than one hire"
    }
  }
}
onboarding_template_apply annotations
{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}
onboarding_progress — Show a hire's progress
Advertised by the server during the last successful anonymous check.

One hire's whole plan: every task with its owner, due date and status, plus the percent complete, the overdue count and what is still outstanding. Pass as_csv for a Pro-only CSV export of the plan.

onboarding_progress input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "hire"
  ],
  "properties": {
    "hire": {
      "type": "string",
      "maxLength": 200,
      "description": "The hire id, e.g. H-0001, or the name when only one carries it"
    },
    "as_csv": {
      "type": "boolean",
      "description": "Return the plan as CSV. Pro only. Default false"
    }
  }
}
onboarding_progress annotations
{
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}
onboarding_overdue — List overdue tasks
Advertised by the server during the last successful anonymous check.
Advertised read-only

Every task that is still outstanding past its due date, across all hires or one hire, with how many days late. Returns at most 500 rows, most overdue first.

onboarding_overdue input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "hire": {
      "type": "string",
      "maxLength": 200,
      "description": "Only this hire's overdue tasks. Omit for every hire"
    }
  }
}
onboarding_overdue annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
license_status — License status
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

license_status input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
license_status annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
license_activate — Activate license
Advertised by the server during the last successful anonymous check.

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.

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

Prompts

2 advertised

onboard_a_hire — Onboard a new hire from day one through day ninety

Advertised by the server during the last successful anonymous check.

Add the hire, build or apply a role template, mark tasks done as they happen, and watch progress and overdue.

name
The new hire's name (required)
role
The role, e.g. engineer or sales (required)
upgrade_to_pro — Explain the upgrade

Advertised by the server during the last successful anonymous check.

Explain what Pro on the onboarding server costs and exactly what the user has to do, without leaving the conversation.

feature
The capped feature that prompted this, if there was one

Resources

2 advertised

contract — The snapshot rule, the task states, the free tier and where this server writes

Advertised by the server during the last successful anonymous check.

Why a hire copies its template, the three task states and what skipped means, the free-tier limits and the one file this server writes.

contract URI
onboarding://contract

MIME type: application/json

pricing — Pricing and upgrade

Advertised by the server during the last successful anonymous check.

What onboarding costs, what Pro unlocks, the checkout link that carries this connection's token, and the one step a person has to take. Machine-readable; read it before telling a user how to lift a free-tier cap.

pricing URI
pricing://onboarding

MIME type: application/json

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1227 ms
95th percentile latency
1227 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1227 ms · metadata changed · 9 tool(s), 2 resource(s), 0 resource template(s), 2 prompt(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http mcp-onboarding https://mcp.zovo.one/mcp/onboarding

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add mcp-onboarding --url https://mcp.zovo.one/mcp/onboarding

Cursor

Merge this server into .cursor/mcp.json in your project, then enable mcp-onboarding in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "mcp-onboarding": {
      "url": "https://mcp.zovo.one/mcp/onboarding"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "mcp-onboarding": {
      "type": "streamableHttp",
      "url": "https://mcp.zovo.one/mcp/onboarding",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start mcp-onboarding and inspect its tools.
VS Code configuration
{
  "servers": {
    "mcp-onboarding": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/onboarding"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http mcp-onboarding https://mcp.zovo.one/mcp/onboarding

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://mcp.zovo.one/mcp/onboarding

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "mcp-onboarding": {
      "serverUrl": "https://mcp.zovo.one/mcp/onboarding"
    }
  }
}

Let your agent find its tools

Find servers like theluckystrike MCP Onboarding from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 5,946