# Ganty MCP (remote · ganty.app)

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

- Trust score: 78/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `ganty.app`: 78/100 (this document), [markdown](https://verifymcp.io/servers/app-ganty-mcp-server/api-mcp.md), [page](https://verifymcp.io/servers/app-ganty-mcp-server/api-mcp)

## Channel facts

- Endpoint: `https://ganty.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1526 tokens (~101/item across 15 items; 15 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 62% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.app-ganty-mcp-server]
url = "https://ganty.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-ganty-mcp-server": {
      "type": "remote",
      "url": "https://ganty.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-ganty-mcp-server --url https://ganty.app/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-ganty-mcp-server:
    url: "https://ganty.app/api/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 77, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-29 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 72, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 71)

First indexed and scored.

## MCP tools (15)

### `list_workspaces` (~21 tokens)

Get all workspaces the authenticated user is a member of.

### `list_projects` (~30 tokens)

List all projects in a workspace (excluding archived).

Input parameters:

- `workspaceId` (string, required): Workspace ID (UUID)

### `create_project` (~108 tokens)

Create a new project in a workspace. Returns the created project. Subject to plan-based project count limits.

Input parameters:

- `color` (string): Hex color (e.g. #3b82f6). Defaults to blue.
- `description` (string)
- `endDate` (string): YYYY-MM-DD. Optional.
- `name` (string, required): Project name
- `startDate` (string): YYYY-MM-DD. Defaults to today.
- `workspaceId` (string, required): Workspace ID (UUID)

### `delete_project` (~41 tokens)

Permanently delete a project. All tasks, milestones, and dependencies inside the project are also removed. This cannot be undone.

Input parameters:

- `projectId` (string, required)

### `list_tasks` (~77 tokens)

List tasks in a project. Supports optional filtering by name (search), status, and assignee.

Input parameters:

- `assigneeId` (string): Filter by assignee profile ID
- `projectId` (string, required): Project ID (UUID)
- `search` (string): Filter task name by case-insensitive substring
- `status` (string)

### `get_task` (~35 tokens)

Get detailed information about a single task, including assignees and dependencies.

Input parameters:

- `taskId` (string, required): Task ID (UUID)

### `list_milestones` (~33 tokens)

List milestones in a project (key dates such as launch or review gates).

Input parameters:

- `projectId` (string, required)

### `create_milestone` (~64 tokens)

Add a milestone (key date) to a project.

Input parameters:

- `color` (string): Hex color (defaults to #f59e0b)
- `date` (string, required): YYYY-MM-DD
- `name` (string, required)
- `projectId` (string, required)

### `create_task` (~152 tokens)

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).

Input parameters:

- `assigneeId` (string): Profile ID of the assignee
- `color` (string): Hex color (e.g. #3b82f6)
- `description` (string)
- `endDate` (string, required): YYYY-MM-DD (exclusive end)
- `name` (string, required)
- `parentId` (string): Parent task ID for hierarchy
- `progress` (number)
- `projectId` (string, required)
- `startDate` (string, required): YYYY-MM-DD
- `status` (string)

### `update_task` (~101 tokens)

Update fields of an existing task. Only provided fields will be modified.

Input parameters:

- `assigneeId` (string|null): null to unassign
- `color` (string)
- `description` (string)
- `endDate` (string): YYYY-MM-DD
- `name` (string)
- `progress` (number)
- `startDate` (string): YYYY-MM-DD
- `status` (string)
- `taskId` (string, required)

### `set_task_progress` (~59 tokens)

Update the progress percentage of a task (0-100). Status is auto-derived: 0=not_started, 1-99=in_progress, 100=done.

Input parameters:

- `progress` (number, required)
- `taskId` (string, required)

### `add_dependency` (~65 tokens)

Add a finish-to-start dependency between two tasks in the same project.

Input parameters:

- `lagDays` (number): Optional lag in days after predecessor finishes
- `predecessorId` (string, required): Task that must finish first
- `successorId` (string, required): Task that can start after predecessor finishes

### `delete_task` (~29 tokens)

Delete a task. Child tasks and dependencies are removed as well.

Input parameters:

- `taskId` (string, required)

### `get_critical_path` (~212 tokens)

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.

Input parameters:

- `as_of_date` (string): YYYY-MM-DD. Start point for projecting remaining work. Defaults to today.
- `business_days` (boolean): 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.
- `project_id` (string, required): Project ID (UUID)

### `reschedule_and_propagate` (~343 tokens)

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.

Input parameters:

- `business_days` (boolean): If true, skip Sat/Sun in duration math. Defaults to false.
- `mode` (string): 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.
- `new_start_date` (string): Absolute new start date as YYYY-MM-DD. Specify exactly one of shift or new_start_date.
- `pinned_task_ids` (array): Additional task IDs to treat as pinned (in addition to progress=100 tasks).
- `respect_dependencies` (boolean): If false, only the named task moves; successors are not cascaded. Default true.
- `shift` (string): Relative shift like '+3d' (push back) or '-2d' (pull earlier). Specify exactly one of shift or new_start_date.
- `task_id` (string, required): Task ID (UUID) to shift

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-ganty-mcp-server/api-mcp#diagnostics

## Score history

- 2026-08-03: 78
- 2026-08-02: 78
- 2026-08-01: 77
- 2026-07-31: 77
- 2026-07-30: 74
- 2026-07-29: 73
- 2026-07-28: 72
- 2026-07-27: 72
- 2026-07-26: 71

## Links

- Remote endpoint: https://ganty.app/api/mcp
- Repository: https://github.com/homareyoshizaki/ganty-mcp
- Website: https://ganty.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-ganty-mcp-server/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-ganty-mcp-server/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/app-ganty-mcp-server/api-mcp