Skip to main content
Glama
Osyanne

projectlibre-mcp

by Osyanne

Related Servers

Alternatives to projectlibre-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude and other LLM clients to read and write Microsoft Project files directly, covering tasks, resources, assignments, dependencies, and critical path information without needing Microsoft Project open.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to read and analyze project schedule files in OmniPlan (.oplx) and Microsoft Project (.mpp) formats, answering questions about tasks, milestones, resources, and progress.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude and other AI agents to build, edit, and analyze Microsoft Project desktop schedules on Windows through natural language, covering tasks, WBS, dependencies, resources, calendars, baselines, critical path, resource leveling, and earned value, with live changes in Project and single-step undo. It also exports results to PDF or CSV and reads project health and time-phased data for S-curves and histograms.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Read-only MCP server for ProjectLibre .pod files that enables finding project files, summarizing Gantt charts, inspecting tasks, and analyzing schedules without opening ProjectLibre.
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects Claude to a project-management account so it can list and manage projects, tasks, comments, and files through eight REST API tools, including creating and updating tasks and adding comments.
      MIT

    TDQS

    B3.2/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: task CRUD, resource assignment, dependency management, critical path, and project summary. No two tools overlap in functionality; descriptions clearly differentiate them.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun pattern (e.g., add_task, list_tasks) except for critical_path, which is a noun phrase. This minor deviation does not significantly impair predictability.

    Tool Count5/5

    With 11 tools covering project creation, task/resource management, dependencies, and analysis, the count is well-scoped for a project management server. Each tool earns its place without being overwhelming.

    Completeness3/5

    The tool surface covers core CRUD for tasks and project creation, but lacks resource update/delete tools and a full project retrieval tool (beyond summary). These gaps may hinder workflows requiring resource lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues