Skip to content

com.loopgantt/mcp-server

by loopgantt.com · remote · local (npm) · no sign-in to list tools · v1.4.0 · published by com.loopgantt

Create scheduled Gantt charts with critical path from a plain-language plan — no account or key.

Changes · 2
CompareRegistry entry

4 tools: 2 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http loopgantt https://loopgantt.com/api/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Changes things 2Claude Code: ask
  • create_ganttCreate a Gantt chart from a task list — no account or API key needed.No findings

    Why it is in this group

    • The name "create_gantt" says "create": a word for a change.
    Description, as the server wrote it
    Create a Gantt chart from a task list — no account or API key needed. YOU author the plan: list the tasks in execution order with realistic working-day durations and dependencies (0-based positions of earlier tasks; use { task, type, lag } for start-to-start/finish-to-finish links or lag). Milestones have duration 0. Only add a dependency where a task truly needs another one finished - independent tasks should run in PARALLEL (share a predecessor, or take no dependencies at all and start at the project start). Group tasks into top-level phases for a structured plan/WBS: the phase task gets isPhase: true, its tasks get parent = the position of the phase. LoopGantt schedules it with its critical-path engine and returns a picture of the chart, the dates, the critical path and a link where the user can view, export (PNG/PDF) and save the chart. Always show the user the link. Tasks with a due date take deadline: YYYY-MM-DD (a marker - the reply reports the fit). Use create_gantt when the user wants a chart to open, export or save; use schedule_project instead for what-if date math where nothing should be stored.
  • schedule_projectCompute a schedule without storing anything: dates, critical path, float and project end for a task list (same input shape as create_gantt; name optional).No findings

    Why it is in this group

    • The name "schedule_project" says "schedule": a word for a change.
    Description, as the server wrote it
    Compute a schedule without storing anything: dates, critical path, float and project end for a task list (same input shape as create_gantt; name optional). Use it to answer "what is the critical path?", "when would this finish?", "how much slack does X have?". Use create_gantt when the user wants a chart they can open.
Only reads 2Claude Code: allow
  • get_templateGet one industry template by slug: its task list with durations, ready to adapt and pass to create_gantt.No findings

    Why it is in this group

    • The name "get_template" says "get": a word for reading.
    Description, as the server wrote it
    Get one industry template by slug: its task list with durations, ready to adapt and pass to create_gantt.
  • list_templatesList LoopGantt's industry project templates with task counts and typical durations.No findings

    Why it is in this group

    • The name "list_templates" says "list": a word for reading.
    Description, as the server wrote it
    List LoopGantt's industry project templates with task counts and typical durations. Pick one, fetch it with get_template, adapt it, then create_gantt.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.4.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http loopgantt https://loopgantt.com/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__loopgantt__list_templates",
      "mcp__loopgantt__get_template"
    ],
    "ask": [
      "mcp__loopgantt__create_gantt",
      "mcp__loopgantt__schedule_project"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as loopgantt. Review it before you use it.