MCP server that wraps the Dagster GraphQL API — manage runs, assets, schedules, sensors, and backfills from any MCP client
SCModeling is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Supply-chain network design via simulation, optimization, and greenfield analysis.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http scmodeling-mcp https://scmodeling.com/mcp
# 2 — ask your agent for something these tools do
# run_simulation, list_models, get_sc_theory and 8 more
SCModeling costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http scmodeling-mcp https://scmodeling.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Run a supply-chain simulation on a bundled SCModeling sample model (sdi-db). Returns metrics, inventory time-series, orders, shipments, routing and BOM. ANTI-FABRICATION: the returned numbers come from a real discrete-event simulation run on the sc-sim engine. Quote them VERBATIM in your reply. Do not round, estimate, average, or compute derived figures from training-data recall. If the user asks
| Parameter | Type | Required | Notes |
|---|---|---|---|
| model_id | string | yes | Which sample model to simulate |
List the bundled SCModeling sample supply-chain models. Returns a catalog with each model's id and a short description. Use this before run_simulation to know which model_id values are valid.
No parameter schema on file.
Reference guide to supply-chain simulation concepts: ordering policies, BOM, FDD formulas, event-driven simulation. Pure static text — no engine call, deterministic output. Use this when the user asks a conceptual 'how does this work' question rather than asking for a number.
No parameter schema on file.
Reference text on supply-chain network optimization — mixed-integer programming (MIP), the structure of decision variables and constraints, the objective function for landed-cost minimization, and the common problem classes (facility selection, sourcing, flow constraints, multi-period, BOM/production, multi-objective). Also covers when to reach for optimization vs simulation. Pure static text — no
No parameter schema on file.
Reference text on greenfield analysis — clean-slate facility-location math. Covers the weighted center-of-gravity (Weber) formulation, Weiszfeld's iterative algorithm, Lloyd's-style alternating location-allocation for N facilities, service constraints (% demand vs % customers within a distance band), and the inverse problem of solving for minimum N. Also covers when to use greenfield vs facility s
No parameter schema on file.
List the bundled SCModeling optimization demos. Returns id + label + one-line summary for each (Tariff, Coffee Co-pack, SSO Basic). Use this before describe_opt_demo or get_opt_result to know which demo_id values are valid. All demos are precomputed sample-only fixtures — for optimization on real client data, the SCModeling desktop tool is the product.
No parameter schema on file.
Full detail on one optimization demo — controls, available scenario keys, sites, fixed parameters, citations, and the key finding the demo illustrates. Use this before get_opt_result to know what scenario_key values are accepted.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| demo_id | string | yes | Which optimization demo to describe |
Get the precomputed result for one scenario of an optimization demo. Returns the verbatim engine output JSON (AMOS for tariff/coffee, SSO output for sso-basic) including the optimal sourcing/production/transport decisions, costs, and any open/close facility variables. ANTI-FABRICATION: every numeric result is verbatim from the optimization engine that ran offline — quote them in your reply, do not
| Parameter | Type | Required | Notes |
|---|---|---|---|
| demo_id | string | yes | Which optimization demo |
| scenario_key | string | no | Scenario key within the demo. Format varies per demo — call describe_opt_demo for the exact valid keys before guessing. Tariff uses 'APAC=<N>' where N is one of 0, 7.5, 25, 50, 100. Coffee uses '<conf |
List the bundled SCModeling greenfield demos. Returns id + label + one-line summary. Currently one demo (US, 189 customer points). Use this before describe_greenfield_demo or get_greenfield_result.
No parameter schema on file.
Full detail on one greenfield demo — region, customer count, available dc_count values, and the score-curve elbow finding. Use this before get_greenfield_result to know what dc_count values are precomputed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| demo_id | string | yes | Which greenfield demo to describe |
Get the precomputed result for one DC count of a greenfield demo. Returns sited DCs (lat/lon + city/state, nearest-city snapped), customer-to-DC assignments, and the score for that DC count. ANTI-FABRICATION: every result is verbatim engine output from greenfield-cli — quote them in your reply, do not round or fabricate cities.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| demo_id | string | yes | Which greenfield demo |
| dc_count | string | yes | Number of DCs to site (2-8) |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install SCModeling or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish SCModeling can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.