Set up MCP integration (operate Ganty from Claude)

Ganty supports the Model Context Protocol (MCP). Connect in one click via Claude's connectors and operate your Gantt chart in natural language from web, iPhone, Android, and desktop — no config file to edit. Free on every plan.

What is MCP?

Model Context Protocol is Anthropic's standard for connecting AI to applications. Connect Ganty as an MCP server and Claude can read or write your data via prompts like "list tasks scheduled for next week's release" or "show me all tasks at 50% progress."

Fastest: connect in one click (recommended — web/mobile/desktop)

With Claude's built-in connectors there's no token to copy and no config file to edit.

1. In Claude, open Settings → Connectors (Customize → Connectors) → “Add custom connector”
2. Enter the server URL: https://ganty.app/api/mcp
3. Approve the Ganty sign-in / authorization screen

Connect once on the web and it syncs to your iPhone, Android, and desktop Claude apps. (Custom connectors on claude.ai are available on Free (up to one), Pro, Max, Team, and Enterprise plans.)

Advanced: connect with an API token (Claude Code, Cursor, manual)

For clients without connector support (Claude Code, Cursor) or manual setups, use an API token as follows.

Step 1: Issue an MCP token in Ganty

Open Dashboard → Settings → API Tokens, then click "Issue new token." The token is shown only once - copy it somewhere safe.

Step 2: Open Claude Desktop's config file

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

Create the file if it doesn't exist.

Step 3: Register Ganty as an MCP server

Add the following under mcpServers.

{
  "mcpServers": {
    "ganty": {
      "type": "http",
      "url": "https://ganty.app/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

Replace YOUR_TOKEN_HERE with the token from Step 1.

Step 4: Restart Claude Desktop

Fully quit and relaunch Claude Desktop. Once recognized, Ganty actions appear in the tool list.

Step 5: Try it from Claude

Test with prompts like:

• "Show me my Ganty projects"
• "List tasks in the e-commerce rebuild project with progress under 50%"
• "Add a new task for deploying on Monday"

Using it from Claude Code

For Claude Code, drop a .mcp.json at the project root with the same config as above - it'll be auto-detected.

Calculation tools: get_critical_path / reschedule_and_propagate

Beyond the CRUD tools (list_tasks/create_task/etc.), Ganty exposes two tools that compute on the server and return the answer as JSON. The LLM doesn't reason over the raw task list — Ganty calculates exact values and hands them back.

get_critical_path

Returns deterministic forward/backward-pass results. Calculation is progress-aware: it projects remaining work from as_of_date, so the answer matches your project's actual state.

Sample prompts:

• "What's the current critical path?"
• "Recompute using business days (skip Sat/Sun)" → business_days: true
• "Project remaining work from July 1, 2026" → as_of_date: "2026-07-01"

Returns: ordered critical-path tasks, per-task earliest/latest start/finish, slack, and projected end date. If a cycle is detected, you get error: "cyclic_dependency" with the cycle path instead of a wrong answer.

reschedule_and_propagate

Simulates the cascade impact of shifting one task. Default mode is dry_run — no DB writes, just computed results.

Sample prompts:

• "If I push the payments implementation by +3 days, when does release ship?"
• "Move milestone X to next Friday and show me the ripple effects. Don't commit yet."
• "That plan looks fine — apply it to the database now" → mode: "commit"

Returns: per-task before/after, project end delta, and any pin conflicts. Tasks with progress=100 are treated as pinned automatically; pushes that would violate them are logged in conflicts and propagation stops there. On mode: "commit", the write happens in a Prisma transaction (all-or-nothing); if any conflict exists, nothing is written.

v1 limitations (calculation tools)

• Dependencies: Finish-to-Start only
• Calendar days by default, business_days: true skips Sat/Sun (no holiday table)
• No resource-level calendars
• Multi-period tasks (extraSegments) are ignored in v1
• Push-only cascade — negative shifts don't pull successors forward

Security note

MCP tokens carry the same privileges as Ganty API keys. Don't share them or commit them to public repos. If a token leaks, you can revoke it instantly from the dashboard.

Related guides and articles

• MCP integration overview
• Server-side calculation engine design
• 7 MCP practical examples
• Generate tasks with AI
• AI project management guide

Related guides and articles

• MCP integration page
• AI task generation
• AI project management guide