projectlibre-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POD_SEARCH_ROOTS | No | Colon-separated directories that list_projects scans for .pod files | ~/Desktop:~/Documents |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | Find ProjectLibre .pod files under the configured search roots. |
| get_project_summaryA | Summarize a .pod project: dates, counts, completion, top-level outline. Args: path: Absolute path to the .pod file (use list_projects to find it). |
| list_tasksA | 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). |
| analyze_scheduleA | 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). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
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.