Loopgantt MCP server
online · 100% uptimecom.loopgantt/mcp-server·v1.4.0Create scheduled Gantt charts with critical path from a plain-language plan — no account or key.
0 stars53 downloads/wk
Reviews
Write oneNobody has reviewed Loopgantt yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Loopgantt tools (4, 1 write)
write = sends, deletes, buys or postscreate_ganttwrite actionFreeCreate 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.
get_templateFreeGet one industry template by slug: its task list with durations, ready to adapt and pass to create_gantt.
list_templatesFreeList LoopGantt's industry project templates with task counts and typical durations. Pick one, fetch it with get_template, adapt it, then create_gantt.
schedule_projectFreeCompute 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.
Public scan report
scanner v0.1.10 · 2026-10-29 · same rubric, same numbers if you re-run it
- Code scan5 source files scanned25/25
- Live reliabilityremote reachable in 1078ms20/20
- Tool poisoning4 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
- Maintenancelast push 58 days ago12/15
- Maintainer identityendpoint served from the registry-verified namespace domain8/10
Findings (1)
- highWrite-action tools reachable without authentication
auth.open-write
How Loopgantt compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 83/100
- higher than 65% of 48,255 servers
- Tools
- 4
- the typical server has 7
- Tools that change things
- 25%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 389 ms
- faster than 38% of 30,031 servers
- Downloads a week
- 53
- more than 44% of 12,191 servers with a package
What its tools let an agent do: 3 read · 1 create
Install Loopgantt in Claude Code, Cursor or VS Code
claude mcp add --transport http mcp-server https://loopgantt.com/api/mcp
Loopgantt: common questions
- Is Loopgantt MCP server safe?
- Mostly: it is graded B (83/100). Read the Loopgantt safety report
- How do I install Loopgantt?
- It runs remotely at loopgantt.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Loopgantt need an API key?
- Yes. The registry entry asks for
LOOPGANTT_API_KEY. - Is Loopgantt maintained?
- The last commit was 64 days ago (2026-09-01). The latest release is v1.4.0.
- Is Loopgantt up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Loopgantt compare with other MCP servers?
- safety score 83/100 (higher than 65% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.