# Ganty MCP server

Source: https://glimind.com/server/mcp-registry%2Fapp.ganty%2Fmcp-server
Registry id: `mcp-registry/app.ganty/mcp-server`
Status: live (checked 2026-10-26T23:18:57.100Z)

## Measurements (30 days)

- Uptime: 99.93%
- Checks: 4930
- Outages (90 days): 4

## Install

```json
{
  "mcpServers": {
    "ganty-mcp-server": {
      "type": "http",
      "url": "https://ganty.app/api/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http ganty-mcp-server https://ganty.app/api/mcp
```

## Tools (15)

- `add_dependency`: Add a finish-to-start dependency between two tasks in the same project.
- `create_milestone`: Add a milestone (key date) to a project.
- `create_project`: Create a new project in a workspace. Returns the created project. Subject to plan-based project count limits.
- `create_task`: 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).
- `delete_project`: Permanently delete a project. All tasks, milestones, and dependencies inside the project are also removed. This cannot be undone.
- `delete_task`: Delete a task. Child tasks and dependencies are removed as well.
- `get_critical_path`: 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 
- `get_task`: Get detailed information about a single task, including assignees and dependencies.
- `list_milestones`: List milestones in a project (key dates such as launch or review gates).
- `list_projects`: List all projects in a workspace (excluding archived).
- `list_tasks`: List tasks in a project. Supports optional filtering by name (search), status, and assignee.
- `list_workspaces`: Get all workspaces the authenticated user is a member of.
- `reschedule_and_propagate`: 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 
- `set_task_progress`: Update the progress percentage of a task (0-100). Status is auto-derived: 0=not_started, 1-99=in_progress, 100=done.
- `update_task`: Update fields of an existing task. Only provided fields will be modified.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.