Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@projectlibre-mcp summarize the Gantt chart for my project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Read-only MCP server for
ProjectLibre .pod files. Lets Claude Code
(or any MCP client) find your project files, summarize Gantt charts, inspect
tasks, and analyze schedules — without opening ProjectLibre.
.pod parsing is done by MPXJ via JPype.
Python 3.12+
Java 11+ on the PATH (required by MPXJ; e.g. brew install --cask corretto)
Related MCP server: Context Weaver
git clone https://github.com/augmdc/projectlibre-mcp.git
cd projectlibre-mcp
python3 -m venv .venv
.venv/bin/pip install -e .From the repo directory:
claude mcp add --scope user projectlibre -- \
"$(pwd)/.venv/bin/python" -m projectlibre_mcp.serverRestart Claude Code and ask something like "Summarize my project Gantt chart". For other MCP clients, configure a stdio server with the same command.
list_projects() — find .pod files under your search roots
get_project_summary(path) — dates, counts, % complete, top-level outline
list_tasks(path, incomplete_only?, start_after?, finish_before?) — tasks
with hierarchy, dates, and predecessors
analyze_schedule(path, as_of?, horizon_days?) — overdue / upcoming /
critical-path tasks
POD_SEARCH_ROOTS — colon-separated directories list_projects scans
(default ~/Desktop:~/Documents). Pass it at registration time with
claude mcp add --scope user --env POD_SEARCH_ROOTS="~/Projects" ....
.venv/bin/pip install -e . pytest
.venv/bin/pytestSet POD_TEST_FILE=/path/to/some.pod to enable the smoke test against a real
file.
Read-only. .pod is ProjectLibre's serialized-Java format; no library can
safely write it. Planned edit path: write MS Project XML for ProjectLibre to
open and re-save as .pod.
MIT
Report overdue, upcoming, and critical-path tasks for a .pod project.
Args: path: Absolute path to the .pod file. as_of: Reference date YYYY-MM-DD (default: today). horizon_days: Window for upcoming tasks (default 30).
Inputs: path (required), as_of, horizon_days.
Summarize a .pod project: dates, counts, completion, top-level outline.
Args: path: Absolute path to the .pod file (use list_projects to find it).
Inputs: path (required).
Find ProjectLibre .pod files under the configured search roots.
Inputs: no named parameters. Returns: result
List tasks in a .pod project with hierarchy, dates, and predecessors.
Args: path: Absolute path to the .pod file. incomplete_only: Drop summary rows and tasks at 100%. start_after: Keep tasks starting on/after this date (YYYY-MM-DD). finish_before: Keep tasks finishing on/before this date (YYYY-MM-DD).
Inputs: path (required), start_after, finish_before, incomplete_only. Returns: result
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 4 tools
Each tool has a distinct and clear purpose: file discovery (list_projects), project overview (get_project_summary), task listing with filters (list_tasks), and schedule analysis (analyze_schedule). There is no overlap or ambiguity among them.
All tool names follow a consistent verb_noun pattern using snake_case (list_projects, list_tasks, get_project_summary, analyze_schedule). This makes the naming predictable and easy to understand.
With 4 tools, the set is well-scoped for a ProjectLibre analysis server. Each tool serves a necessary function without being excessive or insufficient for common project management queries.
The tools cover the core analysis workflow: finding files, summarizing, listing tasks with filters, and performing schedule analysis. Minor gaps exist (e.g., no tool for detailed single-task info or resource data), but these do not hinder typical use cases for a read-only analytical server.
Remote MCP server to read and edit GanttFather projects: tasks, dates, dependencies, critical path.
Read, analyze, and safely edit Microsoft Project MPP files.
MCP server for generating rough-draft project plans from natural-language prompts.
Read-only MCP server for interior design studios: projects, overviews, weekly activity. No writes.
