Skip to main content

Staffing Math

io.github.bsunter93/staffing-mathVersion 0.3.1

Exact staffing math: FTE needed, a monthly hiring plan, and Erlang C queue staffing.

Status

Responds205 msAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.
Last checked
Nov 14, 2026, 14:46 UTC
Latency
205 ms
Remotes responding
1 of 1
Sign-in
No sign-in
Hosting
Hosted outside the EU (detected)
Registry data as of
Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP
https://staffing-math.vercel.app/mcpResponds205 ms
No sign-in

Claude Code

claude mcp add --transport http staffing-math https://staffing-math.vercel.app/mcp

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: staffing-math
Remote MCP server URL: https://staffing-math.vercel.app/mcp

Cursor

{
  "mcpServers": {
    "staffing-math": {
      "url": "https://staffing-math.vercel.app/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"staffing-math","type":"http","url":"https://staffing-math.vercel.app/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

3 tools

Tools of Staffing Math
Read-only
Idempotent
Open world
erlang_staffingFor call center, contact center, phone or chat staffing questions with a service level target, such as 80% answered within 20 seconds. Works out agents needed on a live queue to answer a target share of contacts within a target time, using Erlang C. Give contacts per hour for the interval being staffed (usually the busiest hour) and handle time in seconds. Returns agents needed, the service level at that number and at one fewer, chance of waiting, occupancy, and people to schedule after shrinkage. Use required_fte for case or ticket work with no answer-time target.NoYesYesNo
hiring_planFor hiring plans, headcount plans, and questions about when to open requisitions or how many people to hire as volume grows, shrinks or changes by season. Plans month by month how many requisitions to open so FTE on hand keeps up with FTE needed. A requisition adds capacity only after time to hire and ramp, and attrition removes people every month, so the plan opens reqs ahead of need and flags the months that run short before any new hire can count. Give weekly_volume with monthly_growth (0.05 means 5% a month, compounding), or weekly_volume_by_month. Unknown inputs fall back to stated defaults: current headcount defaults to what month 1 needs, attrition to 0, time to hire to 2 months, ramp to 0. When attrition is assumed, the result also gives the plan at 15% and 30%. Give hires_in_flight for people already hired or in the pipeline. Returns the plan table, totals, the arithmetic, and which inputs were assumed. A hire counts as zero capacity until fully ramped. Hosts that support MCP Apps also draw the plan as a chart with controls that rerun it.NoYesYesNo
required_fteFor questions like "how many people do I need" or "how many FTE does this workload take": cases, tickets, claims, orders or any work measured as volume times handling time. Applies shrinkage and target occupancy together; leaving out occupancy understates the people needed by about 15% at the 85% default. Give weekly volume and minutes per case; shrinkage, target occupancy and hours per week fall back to stated defaults. Returns FTE, people to staff (rounded up), every input marked given or assumed, and the arithmetic with numbers filled in. For volume that changes over time or any question about when to hire, see hiring_plan; for live queues with an answer-time target, see erlang_staffing.NoYesYesNo