Model Context Protocol

Run queueing simulations inside your Claude chat.

QueueSim's MCP server lets Claude (and any MCP-speaking AI) run discrete event simulations directly in conversation. Describe your queue — Claude simulates it and reads back the numbers. Free, no sign-up, no API key.

Install What's in it

https://queuesim.com/mcp/v1

What you can do

Ask Claude queueing questions. Get real numbers back.

Direct M/M/c

Plain-language queueing

"I have 30 calls an hour, each takes 4 minutes, 3 agents — what's my wait?" Claude runs a discrete event simulation and reports wait time, queue length, utilization, and throughput.

Preset scenarios

Four built-in shapes

Single Server, Coffee Shop, ER Waiting Room, Call Center. Run the defaults, or dial in your own numbers. Matches the scenarios on queuesim.com exactly.

Teach the math

Explainers on demand

Little's Law, utilization, Erlang-C, and the ways real queues (abandonment, priority, skills-based routing, breakdowns) break classical M/M/c assumptions.

Install

Three ways in — pick the app you already use.

Claude.ai web

Easiest

Settings → Connectors (or Custom Integrations). Add MCP server:

https://queuesim.com/mcp/v1

No auth. Open a chat and try one of the prompts below.

Claude Desktop

Config file

Edit claude_desktop_config.json:

{
  "mcpServers": {
    "queuesim": {
      "command": "npx",
      "args": ["-y", "mcp-remote",
        "https://queuesim.com/mcp/v1"]
    }
  }
}

Uses the mcp-remote bridge. Restart Desktop.

Cursor

Custom MCP

Settings → Features → Model Context Protocol → Add Custom MCP. Use the same URL:

https://queuesim.com/mcp/v1

Same install pattern works for Windsurf and any other MCP-speaking client.

Six tools

What Claude can call once the MCP is installed.

simulate_mmc

Run a generic M/M/c queue. Inputs: arrival rate (λ), service rate per server (μ), server count (c), optional distributions. Returns per-hour metrics + summary.

list_scenarios

List the four preset scenarios: Single Server, Coffee Shop, ER Waiting Room, Call Center.

describe_scenario

Full detail for one scenario: teaching note, per-hour defaults, supported overrides.

simulate_scenario

Run a preset with optional overrides (servers, arrival rate, service time, days, distributions).

explain_queueing_theory

~500-word primer on M/M/c: Little's Law, utilization, why averages mislead, Erlang-C vs simulation.

explain_advanced_patterns

Textbook-level description of six real-world patterns classical M/M/c can't model — abandonment, priority tiers, overflow, skills-based routing, compound service, server outages.

Try these prompts

Once it's installed, ask Claude any of these.

"I run a call center with 30 calls per hour, each taking 4 minutes to handle. With 3 agents, what's the average wait?" Triggers simulate_mmc. Expect wait ~2 minutes, ρ ≈ 0.67.
"Run the Coffee Shop scenario and tell me where the bottleneck is." Triggers describe_scenario + simulate_scenario. Claude explains the peak staffing question.
"For the ER scenario, what if I staffed 12 overnight instead of 8?" Triggers simulate_scenario with an override. Trade-off lands in the numbers.
"Why does average wait explode as utilization approaches 100%?" Triggers explain_queueing_theory.
"My call center has VIPs who cut the line and agents who go on breaks — can you model that?" Triggers explain_advanced_patterns. Explains priority + outages, points you at ChiAha for custom modeling.

Beyond M/M/c

Real operations usually aren't textbook.

Customers abandon lines. VIPs cut. Skills-based routing, overflow groups, breaks, transfers, after-call work. Each one breaks M/M/c's assumptions in a way that matters. The free MCP can describe these patterns in queueing-theory terms — but running one against your numbers requires a custom discrete event model.

ChiAha has been building exactly that kind of model for 35 years. Reach out and we'll scope a study.

queuesim@chiaha.com