Connect QueueSim and your agent gets 11 tools, among them compare_analytical_vs_simulated, compare_separate_vs_pooled, describe_scenario. It answers at https://queuesim.com/mcp/v1 over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
Run M/M/c queue simulations and four scenarios (call center, ER, coffee shop, single server).
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
compare_analytical_vs_simulated | Run the same M/M/c configuration through BOTH the closed-form Erlang-C formula AND the discrete-event simulator, returning a side-by-side comparison with deltas. Use this when the user is validating QueueSim's engine against textbook values Inputs: arrivalRate, serviceRate, servers, simulationDays |
compare_separate_vs_pooled | Run the classic operations-research teaching demo: pooled queueing (one shared queue, c servers) vs separate queues (c independent queues, one server each, λ/c traffic to each). Both runs have identical total capacity (c × μ) and identical Inputs: arrivalRate, serviceRate, servers, simulationDays |
describe_scenario | Return full details for one preset scenario: title, description, teaching note, peak parameters, and per-hour arrival + staffing arrays. Use this before simulate_scenario to understand the default shape and what overrides make sense. Inputs: name |
explain_advanced_patterns | Return a textbook-level description of six queueing complexity patterns beyond basic M/M/c: abandonment/reneging, priority tiers, overflow routing, skills-based routing, compound service, and server outages. Use this when the user describes |
explain_queueing_theory | Return a ~500-word educational explainer of M/M/c queueing theory: Little's Law, utilization, why averages mislead, how simulation relates to Erlang-C. No inputs. Use this when the user asks a conceptual 'why' or 'how does this work' questi |
interpret_result | Given an M/M/c configuration (arrivalRate, serviceRate, servers) and optionally an observed average wait, returns a queueing-theory framed interpretation: where you sit on the utilization curve, what ρ means in plain language, what one more Inputs: arrivalRate, serviceRate, servers, observedAvgWaitMinutes |
list_scenarios | List the four pre-built QueueSim scenarios. Returns key, title, and one-line description for each (Single Server, Coffee Shop, Grocery Checkout, Call Center). Call this when the user's problem matches one of the preset shapes — use describe |
recommend_staffing | INVERSE of simulate_mmc — given an arrival rate, service rate, and a target average wait time, returns the SMALLEST number of servers needed to meet the target. Use this when the user asks 'how many servers do I need?' / 'what staffing keep Inputs: arrivalRate, serviceRate, targetAvgWaitMinutes, maxServers, simulationDays, arrivalDistribution |
simulate_mmc | Run a generic M/M/c queue simulation. Provide an arrival rate (λ, arrivals/hour), a service rate per server (μ, customers/hour each server can finish), and a server count (c). Optional: distribution shapes, service coefficient of variation, Inputs: arrivalRate, serviceRate, servers, arrivalDistribution, serviceDistribution, serviceCoV |
simulate_scenario | Run one of the four preset scenarios (single, coffee, grocery, callcenter) with optional overrides. Overrides apply UNIFORMLY across open hours — e.g. setting servers=5 on 'coffee' replaces the 4/6/4 staffing pattern with a flat 5 during op Inputs: name, overrides |
simulate_schedule | Run a queueing simulation against an arbitrary 24-hour staffing schedule. Take this when the user describes a custom day shape that doesn't match a preset (e.g., 'my coffee shop is open 6am–10pm with 4 baristas off-peak, 7 at the 8am rush, Inputs: arrivalRates, staffing, serviceTimeMinutes, simulationDays, arrivalDistribution, serviceDistribution |
Every block below points at https://queuesim.com/mcp/v1. Pick your client and copy.
claude mcp add --transport http queuesim https://queuesim.com/mcp/v1
{
"mcpServers": {
"queuesim": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://queuesim.com/mcp/v1"]
}
}
}{
"mcpServers": {
"queuesim": {
"url": "https://queuesim.com/mcp/v1"
}
}
}{
"servers": {
"queuesim": {
"type": "http",
"url": "https://queuesim.com/mcp/v1"
}
}
}{
"context_servers": {
"queuesim": {
"url": "https://queuesim.com/mcp/v1"
}
}
}{
"mcpServers": {
"queuesim": {
"serverUrl": "https://queuesim.com/mcp/v1"
}
}
}{
"mcpServers": {
"queuesim": {
"url": "https://queuesim.com/mcp/v1"
}
}
}name: QueueSim
version: 0.0.1
schema: v1
mcpServers:
- name: QueueSim
type: streamable-http
url: https://queuesim.com/mcp/v1{
"mcpServers": {
"queuesim": {
"httpUrl": "https://queuesim.com/mcp/v1"
}
}
}{
"mcpServers": {
"queuesim": {
"type": "http",
"url": "https://queuesim.com/mcp/v1"
}
}
}{
"mcpServers": {
"queuesim": {
"url": "https://queuesim.com/mcp/v1"
}
}
}goose://extension?url=https%3A%2F%2Fqueuesim.com%2Fmcp%2Fv1&type=streamable_http&id=queuesim&name=QueueSim
It answered our last check on 18 October 2026 in 438 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by queuesim.com and served from queuesim.com, the vendor's own domain: https://queuesim.com/mcp/v1.
11, as returned by the server's own tools/list on 31 August 2026: compare_analytical_vs_simulated, compare_separate_vs_pooled, describe_scenario, explain_advanced_patterns, explain_queueing_theory, interpret_result, list_scenarios, recommend_staffing, and 3 more.
It answered our last check on 18 October 2026 in 438 ms. Over 10 checks since 5 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://queuesim.com/mcp/v1. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.queuesim. Endpoint host: queuesim.com. ARD identifier: urn:air:com.queuesim:mcp:public.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.