Ganty MCP

What Ganty MCP MCP server does

Ganty MCP connects AI clients to the Ganty Gantt chart SaaS. It exposes project information and schedule operations through MCP, allowing an agent to inspect workspaces, projects, tasks, milestones, assignees, and dependencies. Read-only access includes server-side critical-path analysis, while write access adds project, task, milestone, dependency, progress, and rescheduling operations.

The Ganty MCP MCP server is most useful when an agent needs schedule-aware answers rather than simple record retrieval. Its calculation tools return JSON produced by server-side logic, so the model does not need to perform critical-path or dependency-shift arithmetic itself.

How it works

The production endpoint uses Streamable HTTP with JSON-RPC 2.0 over HTTP POST. Clients authenticate with a Bearer token issued from the Ganty dashboard. Tokens have either read or write scope. Read requests are limited to 120 per minute per token, while write requests are limited to 30 per minute.

get_critical_path performs forward and backward CPM passes and reports task timing, slack, projected end date, and total duration. It also detects dependency cycles instead of continuing with an invalid calculation. reschedule_and_propagate can first simulate a shift with dry_run, then apply it with commit. Its cascade pushes successors later when required, respects pinned tasks, and reports conflicts rather than overwriting pinned work. Commit operations are transactional, so conflicts abort the write.

Setup and configuration

Create an MCP token in Ganty under Dashboard, Settings, MCP Integration, and Issue new token. Configure the client with the endpoint URL and an Authorization header containing the token. The README documents configuration for Claude Desktop in claude_desktop_config.json and Claude Code in a project-level .mcp.json file. Restart the client after changing its MCP configuration.

The hosted endpoint is a feature of Ganty workspaces and is available on every Ganty plan, including the Free plan. The documentation repository is licensed under MIT; the hosted Ganty service is not presented as a locally run server.

Tools and capabilities

Read tools include:

• Listing workspaces, projects, tasks, and milestones
• Filtering tasks by name, status, or assignee
• Retrieving a task with assignees and dependencies
• Computing a critical path with slack and duration data

Write tools include project and task CRUD, progress updates, Finish-to-Start dependency creation, milestone creation, and dependency-aware rescheduling. Updating progress also adjusts task status automatically. reschedule_and_propagate is treated as a write tool even for simulations, so dry runs require a write-scope token.

Limitations and notes

The Ganty MCP MCP server supports Finish-to-Start dependencies only. Calendar calculations use calendar days unless business_days is enabled; that option skips Saturdays and Sundays but does not include a holiday calendar. Resource calendars are not supported, and multi-period extraSegments are ignored in calculations.

Tasks at 100 percent progress are automatically pinned, and additional pinned task IDs can be supplied. Cascades are push-only: successors may move later but are not pulled earlier. Calculation responses include a limitations array so clients can account for these constraints.