list_workspaces
Get all workspaces the authenticated user is a member of.
Takes no parameters.

app.gantyPublished by ganty.appOfficial publisherv1.0.0Updated Oct 25, 2026
Gantt chart SaaS with server-side critical path and dependency-aware shift-impact tools, plus CRUD.
Ganty MCP connects an assistant to Ganty's Gantt chart projects, letting it read and edit tasks, milestones and dependencies and compute critical paths server-侧
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/app.ganty%2Fmcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"ganty": {
"type": "http",
"url": "https://ganty.app/api/mcp"
}
}
}Ganty is a Gantt chart SaaS with a built-in Model Context Protocol (MCP) server that lets AI clients like Claude Desktop and Claude Code drive your projects in natural language — and computes critical paths and shift-impact server-side rather than asking the LLM to do math.
Status: v1.0.0 — production endpoint at
https://ganty.app/api/mcp(Streamable HTTP) Free on every Ganty plan including Free.
Most MCP servers expose CRUD over an existing API. Ganty's also exposes calculation tools that compute on the server and return JSON — so the LLM never has to reason about dates, dependencies, or critical paths.
get_critical_path — forward/backward-pass CPM with progress-aware remaining duration. Returns the critical path tasks in order, per-task earliest/latest start/finish, slack, projected end date. Detects cycles before computing and returns error: 'cyclic_dependency' instead of hanging or guessing.reschedule_and_propagate — simulate or commit a task shift. Default mode is dry_run (no DB writes). Push-only cascade respects pinned tasks (anything at progress=100 or in pinned_task_ids) and reports conflicts instead of overwriting. commit mode wraps everything in an all-or-nothing transaction.claude_desktop_config.json) or Claude Code (.mcp.json at project root):
"List my Ganty projects""What's the critical path for the e-commerce rebuild project?""If I push the payments task by +3 days, when does release ship?"Full setup walk-through: https://ganty.app/guide/mcp-integration
reschedule_and_propagate is classified as a write tool even in dry_run mode (it shares the same compute path as commit and we don't want read-only tokens running unlimited simulations).
We prefer explicit non-support over silent wrong answers. Every response from the calculation tools includes a limitations array.
business_days: true skips Sat/Sun only (no holiday table)progress=100 automatically pinned; supply pinned_task_ids for additional pinshttps://ganty.app/api/mcpgnty_...) issued from the Ganty dashboard. Tokens are scoped read or write.reschedule_and_propagate commit mode is wrapped in a Prisma transaction; conflicts abort without writesThe calculation logic lives in pure TypeScript functions backed by 28 golden tests asserting concrete dates and day counts (linear chain shifts, diamond merges, cycle detection within 2 seconds, progress-aware remaining duration, hand-calculated CPM with slack, business-day mode, lag-day handling, push-only cascade).
MIT for this documentation repository. The Ganty server itself is a hosted SaaS; the MCP endpoint is a feature of every Ganty workspace.
Source: README.md at commit df43d13
Get all workspaces the authenticated user is a member of.
Takes no parameters.
List all projects in a workspace (excluding archived).
workspaceIdrequiredCreate a new project in a workspace. Returns the created project. Subject to plan-based project count limits.
namerequiredcolorendDatestartDatedescriptionworkspaceIdrequiredPermanently delete a project. All tasks, milestones, and dependencies inside the project are also removed. This cannot be undone.
projectIdrequiredList tasks in a project. Supports optional filtering by name (search), status, and assignee.
searchstatusprojectIdrequiredassigneeIdGet detailed information about a single task, including assignees and dependencies.
taskIdrequiredList milestones in a project (key dates such as launch or review gates).
projectIdrequiredAdd a milestone (key date) to a project.
daterequirednamerequiredcolorprojectIdrequiredCreate 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).
namerequiredcolorstatusendDaterequiredparentIdprogressprojectIdrequiredstartDaterequiredassigneeIddescriptionUpdate fields of an existing task. Only provided fields will be modified.
namecolorstatustaskIdrequiredendDateprogressstartDateassigneeIddescriptionUpdate the progress percentage of a task (0-100). Status is auto-derived: 0=not_started, 1-99=in_progress, 100=done.
taskIdrequiredprogressrequiredAdd a finish-to-start dependency between two tasks in the same project.
lagDayssuccessorIdrequiredpredecessorIdrequiredDelete a task. Child tasks and dependencies are removed as well.
taskIdrequiredCalculate 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_date, and total_duration_days. v1 limitations: Finish-to-Start dependencies only (Ganty has no other types), calendar days by default (business_days=true skips Sat/Sun but no holiday table), ignores multi-period segments, no resource calendars. Returns { error: 'cyclic_dependency', cycle } if a cycle is detected.
as_of_dateproject_idrequiredbusiness_daysCompute 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 are treated as pinned; pass pinned_task_ids for additional pins. When a pin would be violated, the change is recorded in 'conflicts' and not propagated further. In mode='commit', if any conflicts exist nothing is written (all-or-nothing transaction). Same v1 limitations as get_critical_path: FS only, calendar days by default, no holiday table, ignores multi-period segments.
modeshifttask_idrequiredbusiness_daysnew_start_datepinned_task_idsrespect_dependencies100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
{ "mcpServers": { "ganty": { "url": "https://ganty.app/api/mcp", "headers": { "Authorization": "Bearer YOUR_TOKEN" } } }}