Ganty MCP

app.ganty/mcp-server · v1.0.0 · productivity

Ganty MCP is healthy: it completed an MCP handshake in 2012 ms and exposes 15 tools.

Gantt chart SaaS with server-side critical path and dependency-aware shift-impact tools, plus CRUD.

Endpoint: https://ganty.app/api/mcp (streamable-http)

Repository · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count15
Latency2012 ms
Last checked (UTC)2026-10-15T17:10:14.477Z

Health history

Checked (UTC)StatusLatencyError
2026-10-15T17:10:14.477ZHealthy2012
2026-10-14T16:35:36.535ZHealthy2447

Tools (15)

list_workspacesGet all workspaces the authenticated user is a member of.
list_projectsList all projects in a workspace (excluding archived).
create_projectCreate a new project in a workspace. Returns the created project. Subject to plan-based project count limits.
delete_projectPermanently delete a project. All tasks, milestones, and dependencies inside the project are also removed. This cannot be undone.
list_tasksList tasks in a project. Supports optional filtering by name (search), status, and assignee.
get_taskGet detailed information about a single task, including assignees and dependencies.
list_milestonesList milestones in a project (key dates such as launch or review gates).
create_milestoneAdd a milestone (key date) to a project.
create_taskCreate a new task in a project. Dates must be in YYYY-MM-DD format. End date is exclusive (a 1-day task has end = start + 1 day).
update_taskUpdate fields of an existing task. Only provided fields will be modified.
set_task_progressUpdate the progress percentage of a task (0-100). Status is auto-derived: 0=not_started, 1-99=in_progress, 100=done.
add_dependencyAdd a finish-to-start dependency between two tasks in the same project.
delete_taskDelete a task. Child tasks and dependencies are removed as well.
get_critical_pathCalculate the critical path of a project on the Ganty side and return it as data (don't ask the model to reason over raw task lists). Uses forward/backward CPM with progress-aware remaining duration. Returns critical_path tasks in order, per-task earliest/latest start/finish + slack, project_end_dat
reschedule_and_propagateCompute the downstream impact of shifting a single task. Default is dry_run (no DB writes); set mode='commit' to actually persist the changes. Cascades forward only (no pull): successors are pushed only if their predecessor's new end + lag would violate their current start. Tasks with progress=100 a