Connect the engine to your Claude. In 30 seconds.
Thirteen forensic-schedule tools, callable from your own AI assistant. Not a SaaS, not a wrapper: the same engine that produces every CPP analysis, exposed as an open MCP server.
No signup. No credit card. No analytics tracking your prompts. Paste a URL into your client and the tools show up.
An open standard for letting AI assistants call external tools.
MCP (Model Context Protocol) is Anthropic's open standard for letting AI assistants call external tools. By connecting CPP, your Claude can run a DCMA-14 health check, a windows analysis, or a Monte Carlo simulation on your XER directly. Same tools, same math, no copy-paste.
The CPP server exposes thirteen forensic tools: forensic_windows_analysis, concurrent_delay_matrix, woet_classifier, slip_velocity, collapsed_as_built, time_impact_analysis_fragnet, critical_path_validator, dcma14_health_check, path_explorer, monte_carlo_p50_p80, qramm_maturity, claim_workbench_evidence_ledger, and xer_parser. The endpoint is open: no account and no key. Requests are rate-limited. How the data is handled is set out in the Privacy Policy.
Pick your client. Paste the config. Restart.
Three setup paths below. Same thirteen tools on every client. Current clients use the Streamable HTTP endpoint, /mcp; the older SSE endpoint, /sse, stays up for clients that have not moved on.
Claude (claude.ai and Claude Desktop)
- On a Pro or Max plan, go to Customize → Connectors, click + and then Add custom connector. On a Team or Enterprise plan the owner adds it once under Organization settings → Connectors, and members then connect to it individually.
- Give it a name (e.g. "CPP Forensic") and paste the URL below.
- Save. The tools are available in claude.ai, Claude Desktop and the mobile apps, because Claude reaches the server from Anthropic's cloud rather than from your machine.
Custom connectors are available on the Free, Pro, Max, Team and Enterprise plans, with Free limited to one custom connector (Anthropic help centre, checked 1 October 2026). Ask Claude "What tools does CPP Forensic provide?" to confirm.
Claude Code
- Run the command below once. It registers the server for your user.
- Start a new session. The tools register on start.
Cursor / Cline / other MCP clients
- Find your client's MCP config file. Locations vary by client: Cursor stores it in
~/.cursor/mcp.json, Cline reads from VS Code settings, others differ. See the MCP docs for your client. - Add the snippet below to the client's
mcpServersblock. - Reload your client per its usual instructions. The tools register on the next session.
An older client that only speaks the legacy SSE transport can use https://mcp.criticalpathpartners.ca/sse instead.
Sample prompts to paste into your Claude session.
Each one calls the CPP tools directly. Claude reads your XER, runs the forensic math on the hosted server, and returns the results inline. The engine handles the math. You handle the read.
Other ways in
Want to browse the toolkit before connecting? See Forensic Schedule Analysis. Just want to drop in an XER without the setup? Try the live demo. Want CPP to drive the analysis? Talk to CPP. To see the tools called from Cline and Cursor, read the MCP client walkthrough.
Connect now: paste the URL into your client.
Streamable HTTP for Claude, Claude Code, Cursor, Cline and other current clients. Legacy SSE at /sse for older ones.