Ganty MCP
Server Details
Gantt chart SaaS with server-side critical path and dependency-aware shift-impact tools, plus CRUD.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- homareyoshizaki/ganty-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.7/5 across 15 of 15 tools scored. Lowest: 2.7/5.
Each tool targets a distinct action on a specific resource (project, task, milestone, dependency, workspace). There is no overlap—for example, get_task and update_task are clearly different operations, and list_milestones vs create_milestone are separate actions.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_project, list_tasks, add_dependency). Verbs are uniform and predictable, making the set easy to navigate.
15 tools is well-scoped for a project management server. It covers CRUD for projects and tasks, plus milestones, dependencies, progress tracking, critical path analysis, and rescheduling—neither too few nor too many.
The tool surface covers essential lifecycle operations for projects, tasks, and milestones, including advanced features like critical path and rescheduling. However, minor gaps exist: no update_milestone, delete_milestone, list_dependencies, or remove_dependency; these are noticeable but not critical.
Available Tools
15 toolsadd_dependencyInspect
Add a finish-to-start dependency between two tasks in the same project.
| Name | Required | Description | Default |
|---|---|---|---|
| lagDays | No | Optional lag in days after predecessor finishes | |
| successorId | Yes | Task that can start after predecessor finishes | |
| predecessorId | Yes | Task that must finish first |
create_milestoneInspect
Add a milestone (key date) to a project.
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes | YYYY-MM-DD | |
| name | Yes | ||
| color | No | Hex color (defaults to #f59e0b) | |
| projectId | Yes |
create_projectInspect
Create a new project in a workspace. Returns the created project. Subject to plan-based project count limits.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Project name | |
| color | No | Hex color (e.g. #3b82f6). Defaults to blue. | |
| endDate | No | YYYY-MM-DD. Optional. | |
| startDate | No | YYYY-MM-DD. Defaults to today. | |
| description | No | ||
| workspaceId | Yes | Workspace ID (UUID) |
create_taskInspect
Create 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).
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| color | No | Hex color (e.g. #3b82f6) | |
| status | No | ||
| endDate | Yes | YYYY-MM-DD (exclusive end) | |
| parentId | No | Parent task ID for hierarchy | |
| progress | No | ||
| projectId | Yes | ||
| startDate | Yes | YYYY-MM-DD | |
| assigneeId | No | Profile ID of the assignee | |
| description | No |
delete_projectInspect
Permanently delete a project. All tasks, milestones, and dependencies inside the project are also removed. This cannot be undone.
| Name | Required | Description | Default |
|---|---|---|---|
| projectId | Yes |
delete_taskInspect
Delete a task. Child tasks and dependencies are removed as well.
| Name | Required | Description | Default |
|---|---|---|---|
| taskId | Yes |
get_critical_pathInspect
Calculate 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.
| Name | Required | Description | Default |
|---|---|---|---|
| as_of_date | No | YYYY-MM-DD. Start point for projecting remaining work. Defaults to today. | |
| project_id | Yes | Project ID (UUID) | |
| business_days | No | If true, skip Saturday and Sunday in duration calculations. National holidays are still treated as working days (v1 has no holiday table). Defaults to false. |
get_taskInspect
Get detailed information about a single task, including assignees and dependencies.
| Name | Required | Description | Default |
|---|---|---|---|
| taskId | Yes | Task ID (UUID) |
list_milestonesInspect
List milestones in a project (key dates such as launch or review gates).
| Name | Required | Description | Default |
|---|---|---|---|
| projectId | Yes |
list_projectsInspect
List all projects in a workspace (excluding archived).
| Name | Required | Description | Default |
|---|---|---|---|
| workspaceId | Yes | Workspace ID (UUID) |
list_tasksInspect
List tasks in a project. Supports optional filtering by name (search), status, and assignee.
| Name | Required | Description | Default |
|---|---|---|---|
| search | No | Filter task name by case-insensitive substring | |
| status | No | ||
| projectId | Yes | Project ID (UUID) | |
| assigneeId | No | Filter by assignee profile ID |
list_workspacesInspect
Get all workspaces the authenticated user is a member of.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
reschedule_and_propagateInspect
Compute 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.
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | dry_run (default): compute and return; do not modify DB. commit: write to DB in a single transaction, but only if no conflicts. Audit logged on commit. | |
| shift | No | Relative shift like '+3d' (push back) or '-2d' (pull earlier). Specify exactly one of shift or new_start_date. | |
| task_id | Yes | Task ID (UUID) to shift | |
| business_days | No | If true, skip Sat/Sun in duration math. Defaults to false. | |
| new_start_date | No | Absolute new start date as YYYY-MM-DD. Specify exactly one of shift or new_start_date. | |
| pinned_task_ids | No | Additional task IDs to treat as pinned (in addition to progress=100 tasks). | |
| respect_dependencies | No | If false, only the named task moves; successors are not cascaded. Default true. |
set_task_progressInspect
Update the progress percentage of a task (0-100). Status is auto-derived: 0=not_started, 1-99=in_progress, 100=done.
| Name | Required | Description | Default |
|---|---|---|---|
| taskId | Yes | ||
| progress | Yes |
update_taskInspect
Update fields of an existing task. Only provided fields will be modified.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | ||
| color | No | ||
| status | No | ||
| taskId | Yes | ||
| endDate | No | YYYY-MM-DD | |
| progress | No | ||
| startDate | No | YYYY-MM-DD | |
| assigneeId | No | null to unassign | |
| description | No |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!