Bring an EPA SWMM (.inp) or EPANET (.inp) model into MIKE+ via the mike-plus MCP server — the bridge from an INP builder such as SWMMCanada or agentic-swmm into a MIKE+ database that mike_model_info / mike_run can use. Use when the user has an .inp and wants it in MIKE+. Requires MIKE+ installed + a checked-out license (demo mode caps the model size).
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Creates a new .sqlite from an .inp. SWMM data lands in MIKE+'s SWMM tables
(mss_Node, mss_Link, mss_Project, ... ; subcatchments in msm_Catchment) and the
tool switches the model type to CS_SWMM so the imported simulation setup is the
active one. mike_model_info then reports the mss_* counts and setups.
mike_import_swmm — {inp, out_sqlite, kind?='swmm'|'epanet', overwrite?, srid?, projection?} → {sqlite, inp_used, patched_outfalls_gated[], active_model, active_simulation, unit_system, simulations[], counts{nodes,links,catchments}, inp_scan}.[OUTFALLS] rows without the optional Gated column (O1 90 FREE, valid for EPA SWMM which assumes NO) with an opaque "Error importing from SWMM file." The tool writes a patched COPY <name>.mikeplus.inp next to out_sqlite (adds NO), imports that, and lists the rows in patched_outfalls_gated. Your original .inp is never modified.m_ModelSetting.ModelNo = 2 (SWMM) so active_model = CS_SWMM and the imported mss_Project setup is active.overwrite defaults to false; the tool refuses to clobber an existing .sqlite..inp (FILE "rain.dat" time series) are not copied; keep them next to the .inp and check inp_scan.TIMESERIES vs what the model expects.mike_model_info (expect CS_SWMM, mss_* counts) → copy the folder → mike_run. Running an imported SWMM-type model through mike_run has not been verified live yet (license); gate on status as always and report what you see.kind='epanet') uses the same call; the model type is left as MIKE+ sets it (report active_model).mike_import_swmm {inp, out_sqlite: runs/<case>/00_model/<name>.sqlite}
mike_model_info {sqlite} -> CS_SWMM, setups, counts
mike_run {sqlite} (license) -> result files -> mike-results / mike-plot
mike_manifest_write {model, inputs: [inp, inp_used], ...}
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Record provenance for an Agentic MIKE+ step via the mike-plus MCP server — a manifest.json tying the model copy, inputs, edits, run QA status, result files and figures together, each file with a sha256. Use at the end of every run/compare/plot task (successful or failed) so the work can be audited, re-compared or reproduced later. No license required.
The English summary is being prepared. Showing the original description.
Compare two MIKE+ runs via the mike-plus MCP server — baseline vs scenario, before vs after a parameter edit — to say WHERE a change mattered and BY HOW MUCH (delta peak, delta volume, timing shift, RMSE/NSE) and to draw the overlay hydrograph. Use whenever two .res1d files of the same model exist or a re-run just finished. Comparing needs no license; producing the second run does.
The English summary is being prepared. Showing the original description.
Standard operating procedure for an auditable, headless MIKE+ workflow via the mike-plus MCP server — how to plan, copy, run, QA-gate, compare, plot, audit, and safely stop. Use FIRST whenever an agent is handed a MIKE+ model (.sqlite) or result (.res1d) plus a plain-language goal; it picks the operating mode and tells the agent which mike-* skill to open next and in what order.
The English summary is being prepared. Showing the original description.
Inspect a MIKE+ .sqlite model via the mike-plus MCP server — active simulation/scenario/model type, unit system, the list of simulation setups and scenarios, element counts — and switch the active scenario. Use when an agent needs to understand a MIKE+ model before running or editing it, or must run a scenario prepared in the GUI. Requires MIKE+ installed + a license.
The English summary is being prepared. Showing the original description.
Read and modify MIKE+ model parameters via the mike-plus MCP server — inspect or change values in any model table (pipe Diameter/Manning in msm_Link, node levels in msm_Node, catchment properties in msm_Catchment, etc.). Use when an agent must identify a current parameter and change it before re-running. Requires MIKE+ + license; mutating tools must run on a copy.
The English summary is being prepared. Showing the original description.
Produce publication-style figures from MIKE+ .res1d results via the mike-plus MCP server — a stacked rainfall-runoff hydrograph, a single time series, a network map, a baseline-vs-scenario overlay, or a longitudinal profile (bed / crown / ground / max water level along a pipe string), in the house style (Arial 12, ticks inward, SI units, no title). Use when an agent must render MIKE+ results as a PNG without opening the GUI. No license required.
The English summary is being prepared. Showing the original description.