Skip to main content
Glama
Osyanne

projectlibre-mcp

by Osyanne
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
summarize_projectB

Resumen del proyecto: nombre, fechas, # tareas/recursos e hitos.

list_tasksB

Lista las tareas con id, nombre, fechas, duración, %, predecesoras y recursos.

get_taskC

Detalle de una tarea por su id (uniqueID).

list_resourcesC

Lista los recursos y sus asignaciones (tarea, unidades, trabajo).

critical_pathA

Ruta crítica y holgura (slack) por tarea. Requiere un archivo ya calendarizado.

create_projectA

Crea un proyecto desde cero y escribe un .xml que se abre en ProjectLibre.

start_date en formato YYYY-MM-DD. tasks: lista de objetos con
name, duration_days y opcionales predecessors (índices 1-based o nombres),
resource, percent_complete, is_milestone. out debe terminar en .xml.
add_taskC

Agrega una tarea a un proyecto y guarda el resultado en .xml (out o el .xml de entrada).

update_taskB

Modifica campos de una tarea (name, duration_days, percent_complete, is_milestone, start).

remove_taskC

Elimina una tarea por id y guarda el resultado en .xml.

set_dependencyB

Crea una dependencia entre tareas. type ∈ {FS, SS, FF, SF}.

assign_resourceC

Asigna un recurso a una tarea (lo crea si no existe) y guarda en .xml.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

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

Resources