Hire and run AI employees: browse the published catalog, hire one onto your brand, list the team you already pay for, check provisioning, cancel, and equip a profession onto a live hire.

Install

npm install -g @opvs-ai/mcp-employees

Provides the opvs-mcp-employees binary.

The @opvs-ai scope resolves to different registries depending on your .npmrc. This package is published to both public npm and npm.opvs.ai; if you have a scope pin, note that it beats --registry on both npm view and npm install.

Auth (one-time)

Shares ~/.opvs/config.json with @opvs-ai/cli. If you already ran opvs auth request, you're done. Otherwise:

npm install -g @opvs-ai/cli
opvs config set api_url https://app.opvs.ai
opvs auth request --workspace <slug> --email <admin-email>
# admin clicks Approve in the email

MCP client config

Antigravity / Claude Desktop / Cursor

{
  "mcpServers": {
    "opvs-employees": {
      "command": "opvs-mcp-employees"
    }
  }
}

Optionally pin a workspace via env:

{
  "mcpServers": {
    "opvs-employees": {
      "command": "opvs-mcp-employees",
      "env": { "OPVS_WORKSPACE": "my-slug" }
    }
  }
}

What's in it

7 tools:

Tool	What it does
`employees_catalog_search`	Browse the published AI Employee catalog (filter by category, price band, featured, keyword)
`employees_employee_get`	Full public profile for one employee, by slug
`employees_team_list`	The hires this brand already pays for
`employees_hire_get`	One hire's status — poll this until `provisioning` becomes `active`
`employees_hire`	Hire an employee onto your brand
`employees_cancel`	Cancel a hire at period end
`employees_equip_profession`	Equip a profession onto a live hire

employees_hire spends money and consumes a plan seat. Confirm with a human before calling it. It returns status: "provisioning", not a working agent — poll employees_hire_get until active.

The brand is always resolved from your own token. Passing a brand id from a self-serve token is ignored.

Scope — customer surface only

This package ships the employees skill (tier: beta, customer-facing). It deliberately does not ship employees-persona, whose marketplace package is tier: internal — the operator surface for authoring a hired employee's SOUL.md / AGENTS.md / TOOLS.md / USER.md and daily memory. Those tool definitions are available to embedders via @opvs-ai/skills-sdk/employees-persona.

Version ⇄ tool surface

This package pins @opvs-ai/skills-sdk to an exact version from 0.1.0 onward, so a given mcp-employees version always resolves to the same tool surface.

The tool definitions live in skills-sdk, not here. Had the dependency been a caret range, publishing a new SDK would silently change the surface of every already-published mcp-employees version — making the version number a lie and version-specific bug reports unfalsifiable. See AgentCLI LEARNINGS #29.

Why this instead of @opvs-ai/mcp?

The full @opvs-ai/mcp package exposes 400+ tools — fine for Claude Code, but rejected by clients with per-server tool caps (Antigravity: 100). This package ships only Employees.

For AgentBoard or AgentDocs, install @opvs-ai/mcp-agentboard or @opvs-ai/mcp-agentdocs alongside.