Koskamo

PFlow Sim MCP

Document v1 · published by Koskamo · updated 2026-10-05

Original source

An official MCP server for PFlow's simulation engine that allows AI assistants to build, diagnose, and compare Petri-net models for cost-benefit analysis. It enables users to run seeded, repeatable simulations to rank decision knobs by their actual measured effect, supporting both public read-only tools and authenticated model creation via OAuth 2.1.

  • Operator: PFlow
  • Endpoint: https://sim.pflow.xyz/mcp
  • Transport: streamable-http
  • Sign-in: No sign-in
  • Category: Data and analytics
  • Use cases: Run seeded simulations to compare cost-benefit scenarios; Diagnose Petri-net models to identify ineffective capacity; List and retrieve existing simulation models; Generate synthetic event logs from simulation runs
  • Tools: sim_accept_migration, sim_bind, sim_calibrate, sim_canonical, sim_check_witness, sim_classify, sim_code_to_flow, sim_compare, sim_components, sim_compose, sim_conformance, sim_create_collection, sim_create_model, sim_create_system, sim_crosscheck, sim_dataset, sim_delete_model, sim_diagnose, sim_diff, sim_distill, sim_edges, sim_evaluate, sim_extend, sim_get_binding, sim_get_model, sim_invariants, sim_license_model, sim_link, sim_list_bindings, sim_list_models, sim_map_get, sim_map_list, sim_map_put, sim_migration_offers, sim_my_sheets, sim_neighbors, sim_optimize, sim_param_heatmap, sim_prompt, sim_propose_types, sim_prove, sim_publish, sim_publish_app, sim_publish_compare, sim_query, sim_reach, sim_receipt, sim_refine, sim_reroll, sim_run_pipeline, sim_scenario, sim_supersede_model, sim_system, sim_verify
  • Documentation: https://sim.pflow.xyz/
  • Directory listing: https://koskamo.com/explore/pflow-sim-mcp
  • Also known as: PFlow Sim MCP MCP; pflow-sim-mcp

Source and provenance

Original source
sim.pflow.xyz
Published on Koskamo by
Koskamo
Citation version
Document v1
Reuse
Check the original source’s reuse terms.

This record mirrors the MCP server directory listing and updates when the listing changes. To correct it, suggest an edit on the listing.

Version history

  1. Synced from the directory

    Version 3

  2. Synced from the directory

    Version 2

  3. Synced from the directory

    Version 1