A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
Cpp Cpm Engine 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.
13
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Forensic scheduling MCP for Primavera P6 (XER): AACE windows, DCMA-14, Monte Carlo, TIA.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http cpp-cpm-engine-mcp https://mcp.criticalpathpartners.ca/mcp
# 2 — ask your agent for something these tools do
# forensic_windows_analysis, concurrent_delay_matrix, woet_classifier and 10 more
Cpp Cpm Engine costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DAAll 1 server
danafitkowski1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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.
Claude Codedeclared by this listing
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 cpp-cpm-engine-mcp https://mcp.criticalpathpartners.ca/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
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.
What you approve
13 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 forensic windows analysis (AACE RP 29R-03 §3.3, MIP 3.3 Observational / Dynamic / Contemporaneous As-Is) across multiple Primavera P6 XER snapshots and return the full analysis dict. This is the headline forensic tool — it computes per-window completion shifts, per-window slip registers (per-activity slip with a critical
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schedules | array | yes | — |
| project_name | string | no | — |
| baseline_idx | integer | no | — |
| entitlement_milestone | string | no | — |
| output_dir | string | no | — |
Build the per-window x per-party concurrent-delay attribution matrix from a chronological list of XER snapshots. Implements the per-window concurrency view per AACE RP 29R-03 §3.3.I (apportionment) and §4.2 (concurrency). Where `forensic_windows_analysis` answers "how many days does each party own across the whole project?", this tool
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schedules | array | no | — |
| xer_paths | array | no | — |
| xer_contents | array | no | — |
Worked-vs-On-time Execution Timeline (WOET) per-activity day-by-day classification of as-built execution against baseline. For each pairable activity (matched by `task_code`), classifies execution into 4 day-states: - PROGRESS: work performed during the baseline-planned window - GAIN: work performed BEFORE the baseline window o
| Parameter | Type | Required | Notes |
|---|---|---|---|
| baseline_xer_path | string | no | — |
| actual_xer_path | string | no | — |
| baseline_xer_content | string | no | — |
| actual_xer_content | string | no | — |
| today | string | no | — |
Per-window slip velocity & acceleration trend across XER snapshots. Computes three signed metrics per window from the underlying forensic windows analysis: - slip_velocity_days_per_day: completion shift / window duration (positive = slipping, negative = recovering). Numerator is the WORKING-day completion shift. The
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schedules | array | no | — |
| xer_paths | array | no | — |
| xer_contents | array | no | — |
Collapsed As-Built / But-For analysis on a post-impact XER. Implements AACE RP 29R-03 §3.8 Modeled / Subtractive / Single Base method (paired with MIP 3.3 Windows for the dual-method gap report per SCL §11.5). Validates a forensic windows analysis (MIP 3.3) by independently computing the same project drift via subtractive removal of dela
| Parameter | Type | Required | Notes |
|---|---|---|---|
| as_built_xer_path | string | no | — |
| delay_events | array | no | — |
| as_built_xer_content | string | no | — |
| output_dir | string | no | — |
| project_name | string | no | — |
| removal_method | string | no | — |
| contractor_filter | boolean | no | — |
Time Impact Analysis (TIA) — prospective fragnet insertion into a pre-impact baseline schedule. Supports two modes. Single-base mode (legacy): supply `baseline_xer_path or baseline_xer_content`. All fragnets are inserted into the same shared baseline XER and impact is measured against that shared baseline. The result carries a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| baseline_xer_path | string | no | — |
| fragnets | array | no | — |
| baseline_xer_content | string | no | — |
| per_event_bases | object | no | — |
| output_dir | string | no | — |
| project_name | string | no | — |
Critical-path validation, logic health, and DCMA-14 assessment of a Primavera P6 schedule. Runs the CPP critical-path validator: checks for false criticality, constraint-driven CP segments, open ends, broken logic, and surfaces a DCMA-14 block with the 14 metrics (logic, leads, lags, FS%, hard constraints, high float, high du
| Parameter | Type | Required | Notes |
|---|---|---|---|
| xer_path | string | no | — |
| project_index | integer | no | — |
| profile | string | no | — |
| baseline_xer_path | string | no | — |
| xer_content | string | no | — |
| baseline_xer_content | string | no | — |
Full Schedule Health Dashboard HTML report — DCMA-14 + CPLI + BEI + variance/slip register against the baseline. Wraps the CPP Schedule Health Review skill, which produces a self-contained ~1.3 MB HTML dashboard. The dashboard renders DCMA metrics, charts, baseline-vs-current variance, slip register, GAO/AACE compliance bands, and a repr
| Parameter | Type | Required | Notes |
|---|---|---|---|
| current_xer_path | string | no | — |
| baseline_xer_path | string | no | — |
| current_xer_content | string | no | — |
| baseline_xer_content | string | no | — |
| output_path | string | no | — |
| timeout_seconds | integer | no | — |
| debug | boolean | no | — |
| return_html_inline | boolean | no | — |
Logic-trace driver-chain explorer — answers "WHY is this activity critical?" and "WHAT does it drive?". Traces driving predecessors backward from a target activity to project start (the "why critical" chain) and/or driving successors forward to project finish (the "what it drives" chain). Detects constraint-driven artificial criticality
| Parameter | Type | Required | Notes |
|---|---|---|---|
| xer_path | string | no | — |
| target_activity_codes | array | no | — |
| direction | string | no | — |
| include_near_critical | boolean | no | — |
| output_dir | string | no | — |
| xer_content | string | no | — |
Monte Carlo Schedule Risk Analysis — P10/P50/P80/P90 completion-date forecast for a Primavera P6 schedule. Implements an AACE-style quantitative SRA (the same math as CPP's browser Tool_11 Portfolio Risk Engine, scripted Python counterpart). For each iteration, every activity duration is sampled from the chosen distribution (Triangular,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| xer_path | string | no | — |
| iterations | integer | no | — |
| distribution | string | no | — |
| optimistic_pct | number | no | — |
| most_likely_pct | number | no | — |
| pessimistic_pct | number | no | — |
| seed | integer | no | — |
| output_dir | string | no | — |
| xer_content | string | no | — |
QRAMM-aligned maturity reading for an SRA result. Places a Schedule Risk Analysis run (from `monte_carlo_p50_p80` or any equivalent dict) on the five named maturity levels of AACE RP 122R-22 (Quantitative Risk Analysis Maturity Model), section 3: level 1 Reactive, level 2 Ad-hoc, level 3 Centralized, level 4 Dynamic, level
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sra_result | object | yes | — |
Forensic claim workbench — analyzes a folder of mixed evidence (XER chain + MSG/PDF/DOCX/XLSX correspondence) and produces a unified workbench dashboard. Built from the real-world workflow where forensic delay analysis starts from a folder containing schedule updates, owner correspondence, RFIs, change orders, and meeting min
| Parameter | Type | Required | Notes |
|---|---|---|---|
| folder_path | string | no | — |
| evidence_files | no | — | |
| output_dir | string | no | — |
| project_name | string | no | — |
| original_baseline_xer_filename | string | no | — |
| contract_form | string | no | — |
| run_forensic | boolean | no | — |
Parse a Primavera P6 XER file and return a TABLE SUMMARY (not the full row-level data — XER row dumps explode the MCP context window). For each table in the XER, returns the table name, field list, and record count. Per-row data is intentionally omitted — for forensic / DCMA / windows analysis use the dedicated tools (`forensic_windows_analysis`,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| xer_path | string | no | — |
| xer_content | string | no | — |
Free
$0 forever
- 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 Cpp Cpm Engine or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
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: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. 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 2.9.43.
2.9.43
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish Cpp Cpm Engine can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.