project-mcp

🇺🇸 English · 🇧🇷 Versão em português

Model Context Protocol (MCP) server that exposes Microsoft Project files to LLM clients like Claude Desktop and Claude Code. Reads schedules, resources, dependencies, critical-path data, and baseline variance — and adds AWP (Advanced Work Packaging, CII) and LPS (Last Planner System, Lean) layers for work-package planning, constraints, weekly commitments and PPC tracking. All local, no cloud calls, no Microsoft Project license required.

Why

Construction, engineering, and BIM workflows live in Microsoft Project schedules. This server lets your LLM:

• Inspect a project schedule and answer questions about it (deadlines, critical path, resource overload).

• Cross-reference task data with quantities from BIM models or with cost data from Power BI dashboards.

• Generate JSON exports for downstream automation (dashboards, reports, ETL pipelines).

It's read-only by design. Project edits stay where they belong: in Microsoft Project itself.

Related MCP server: RevitMCPBridge2026

Requirements

• Python 3.11+

• An MCP-compatible client (Claude Desktop, Claude Code, etc.)

• For .xml (MSPDI): no extra dependencies

• For .mpp (native Microsoft Project): the optional [mpp] extra (requires a JVM via the mpxj package)

Installation

Option A — uv (recommended)

git clone https://github.com/jeffmodeler/project-mcp.git
cd project-mcp
uv sync

Option B — pip

pip install git+https://github.com/jeffmodeler/project-mcp.git

For .mpp support:

uv sync --extra mpp
# or
pip install "project-mcp[mpp] @ git+https://github.com/jeffmodeler/project-mcp.git"

Claude Desktop integration

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "project-mcp": {
      "command": "uv",
      "args": [
        "--directory",
        "C:\\path\\to\\project-mcp",
        "run",
        "project-mcp"
      ]
    }
  }
}

Restart Claude Desktop. The 35 tools become available in any conversation (13 core MS Project + 10 AWP + 12 LPS).

Tools

Exporting .mpp to MSPDI XML

If you don't want to install Java for the optional mpp extra, export your schedule from Microsoft Project as XML:

1. Open the .mpp file in Microsoft Project.

2. File → Save As → Save as Type → XML Format (*.xml).

3. Point load_project at the resulting .xml.

The XML format is the official Microsoft Project Data Interchange (MSPDI) schema and contains tasks, resources, assignments, predecessors, baseline, and most of the project metadata.

Example prompts

After loading a project, ask Claude:

Load the project at C:\schedules\obra-acme.xml
Give me the critical path with total duration in days.
Which resources are overallocated and by how much?
List the 5 tasks with the largest baseline variance.
Export the full project to C:\reports\obra-acme.json

AWP — Advanced Work Packaging

Construction Industry Institute (CII) methodology. Breaks execution into aligned packages across engineering, procurement and field:

CWA (Construction Work Area) → CWP (Construction Work Package)
                                     ↓
                               IWP (Installation Work Package)

Focus: path of construction + readiness (nothing starts in the field until materials, documents and access are available).

AWP tools

LPS — Last Planner System

Lean Construction method with five planning levels:

Master → Phase (pull plan) → Lookahead (N weeks, clears constraints)
                              → WWP (Weekly Work Plan) → Daily huddle

Key metric: PPC (Percent Plan Complete) — commitments kept / commitments made.

LPS tools

Constraint types: material, document, information, design, labor, equipment, access, permit, prerequisite, other.

Variance reasons: weather, design_change, material_delay, labor_unavailable, equipment_breakdown, rework, permit, prerequisite_incomplete, scope_change, other.

Sidecar storage

The .mpp/.xml file remains authoritative (read-only preserved). Next to the project file, an <name>.awp/ folder holds metadata that Microsoft Project does not represent well:

C:\schedules\
├── obra-acme.mpp              ← authoritative schedule (never modified)
└── obra-acme.awp/             ← sidecar folder, created on demand
    ├── awp.json               ← CWA / CWP / IWP hierarchy
    └── lps.json               ← phases, pull plans, constraints, WWPs

Every write updates updated_at (ISO 8601 UTC) in the JSON.

Development

uv sync --extra dev
uv run pytest -v
uv run ruff check src tests

License

MIT — see LICENSE.