moncapro
Critical path (CPM) project planning with Monte Carlo simulation, scenarios and MCP interface.
Projects are plain JSON files. moncapro computes the critical path in working days, levels
resources (people, vehicles), respects vacation, part-time work and holidays, compares
what-if scenarios and simulates schedule risk with Monte Carlo runs. An MCP server lets AI
clients (e.g. Claude Code) build and calculate projects through tools.
A desktop editor built on moncapro is sproject (Dear PyGui).
Installation
pip install moncapro # core: model, CPM, leveling, simulation, TXT/JSON/Markdown export
pip install "moncapro[all]" # + Excel, HTML, SVG, Plotly charts, MCP server
Extras: excel, html, svg, charts, mcp, all. Python 3.12 or newer.
Quickstart
from moncapro import load_project, build_schedule
project = load_project("my_project.json")
schedule = build_schedule(project)
print(schedule.cpm.project_duration)
Command line:
moncapro --project my_project.json --export json,txt,md
MCP server (needs the mcp extra):
moncapro-mcp --http --port 8765
claude mcp add --transport http moncapro http://127.0.0.1:8765/mcp
Example projects ship with the package (moncapro.paths.get_examples_dir()).
Configuration
The packaged cfg/ (working hours, calendar, export layout) is used by default. Override it with
a directory of your own: --cfg-dir or MONCAPRO_CFG.
| Variable | Meaning | Default |
|---|---|---|
MONCAPRO_CFG |
configuration directory | packaged cfg/ |
MONCAPRO_RESULTS |
export output | ./results |
MONCAPRO_WORK |
working files, backups | current directory |
MONCAPRO_LOG |
log files | ./log |
MONCAPRO_DATA |
CLI input projects | ./data |
Documentation
| Topic | English | Deutsch |
|---|---|---|
| Command line | doc/en/cli.md | doc/de/cli.md |
| Project file format | doc/en/project-format.md | doc/de/projektformat.md |
| Configuration | doc/en/configuration.md | doc/de/config_doc.md |
| AI interface (MCP) | doc/en/ai-interface.md | doc/de/ki-schnittstelle.md |
| Examples | doc/en/examples.md | doc/de/examples.md |
| Critical path method, dependency types, actuals and baseline | doc/de/critical-path-method.md, doc/de/dependency_types.md, doc/de/termine-und-ist.md |
Pre-computed example results: doc/result_examples/.
Development
python -m venv .venv && .venv/bin/pip install -e ".[dev]" # Windows: .venv\Scripts\pip
python -m pytest
License
MIT, see LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for moncapro 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| moncapro-0.1.1.tar.gz | 318.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| moncapro-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 456.1 kB
Release files / moncapro-0.1.1.tar.gz
| Download URL | moncapro-0.1.1.tar.gz |
|---|---|
| Size | 318.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0a20dd21552da50812210dca4b6ae77b26410ea233b557026d2db8145feb6af0
|
|
BLAKE2b-256 checksum How to use checksums |
df74ed297121f95ddfff42a8f9a908c869261b85fbb7008ad30f812d80d8035e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / moncapro-0.1.1-py3-none-any.whl
| Download URL | moncapro-0.1.1-py3-none-any.whl |
|---|---|
| Size | 137.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ce9e7ec7d3a93a659d55b5071eafc427a733a4fbd4d41361342c7c963663a061
|
|
BLAKE2b-256 checksum How to use checksums |
ea9f37f20b66b560b84cba65276c5f87d9d2ac94eb53c6c558eac1bcb57361f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logSecurity for moncapro 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for moncapro-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
