Wire It Into Your Own Claude

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.

What is MCP

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. Public, no auth, no rate-limit games.

Setup

Pick your client. Paste the config. Restart.

Three setup paths below. Same thirteen tools either way — only the transport differs (Streamable HTTP for claude.ai web, legacy SSE for everything else).

Claude Desktop

For the Mac / Windows app

Open your config file. On Mac: ~/Library/Application Support/Claude/claude_desktop_config.json. On Windows: %APPDATA%\Claude\claude_desktop_config.json. (If the file doesn't exist, create it.)
Paste the snippet below into the file. If you already have an mcpServers block, just add the cpp-forensic entry alongside your existing servers.
Save the file and fully quit and restart Claude Desktop (closing the window isn't enough — quit from the menu bar / system tray).

{
  "mcpServers": {
    "cpp-forensic": {
      "url": "https://mcp.criticalpathpartners.ca/sse"
    }
  }
}

After restart, the thirteen forensic tools appear in Claude's tool palette. Ask Claude "What MCP tools are available from cpp-forensic?" to confirm.

Claude.ai (web)

For the browser version at claude.ai

In claude.ai, click your profile icon and go to Settings → Connectors.
Click Add custom connector. Give it a name (e.g. "CPP Forensic") and paste the URL below. Note this is /mcp, not /sse — the web client uses Streamable HTTP, not legacy SSE.
Save. The tools become available immediately — no restart, no reload.

https://mcp.criticalpathpartners.ca/mcp

Custom connectors require a Claude Pro or Max plan. Once added, they're available across every conversation in your account.

Cursor / Cline / other MCP clients

For developer tools and other MCP-aware editors

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.
Drop the same snippet below into the client's mcpServers block (same format as Claude Desktop — the SSE transport works for any client that speaks the legacy MCP protocol).
Reload your client per its usual instructions. The tools register on the next session.

{
  "mcpServers": {
    "cpp-forensic": {
      "url": "https://mcp.criticalpathpartners.ca/sse"
    }
  }
}

If your client supports Streamable HTTP transport (newer clients), use the /mcp endpoint from Step 02 instead — it's the modern protocol and slightly more resilient over flaky connections.

After You Connect

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.

DCMA-14 Health Check

After CPP is connected, ask Claude: "Run a DCMA-14 health check on the XER at /Users/me/projects/baseline.xer and current.xer. Show me the failed criteria with activity counts."

Forensic Windows Analysis

After CPP is connected, ask Claude: "Generate a forensic windows analysis comparing baseline.xer to monthly updates Aug-Dec 2025. List per-window slip and concurrency."

Monte Carlo SRA

After CPP is connected, ask Claude: "Run a Monte Carlo schedule risk analysis with 5000 iterations on schedule.xer. Give me P50/P80 completion dates and a sensitivity tornado."

Evidence Ledger

After CPP is connected, ask Claude: "Build the evidence ledger from /path/to/claim_folder. Show me the schedule chain-diff and trust score."

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.

Connect now — just paste the URL into your client.

Streamable HTTP for claude.ai web. Legacy SSE for Claude Desktop, Cursor, Cline, and everything else.

https://mcp.criticalpathpartners.ca/sse

Try It Live — Drop Your XER → See What's Connectable