com.loopgantt/mcp-server
v1.4.0Create scheduled Gantt charts with critical path from a plain-language plan — no account or key.
Endpoint health
online- Last checked
- 11/20/2026, 7:16:32 AM
- Latency
- 84 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.loopgantt%2Fmcp-server
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.loopgantt/mcp-server": {
"url": "https://loopgantt.com/api/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
21 shown · authentication unknown
add_comment
Leave a comment on a task in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key) — notes, handoffs between agents, questions for a person. It shows in the task timeline, notifies the task watchers and @-mentioned people, and fires the comment.posted webhook.
Schema valid · SHA-256 d82acd870a5d…
View input schema
{ "type": "object", "properties": { "taskId": { "type": "string", "description": "Task id from list_tasks" }, "content": { "type": "string", "description": "The comment text (up to 10 000 characters)" }, "parentId": { "type": "string", "description": "Reply to this top-level comment id (from list_comments)" } }, "required": [ "taskId", "content" ] }complete_task
Mark one task done in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key). LoopGantt treats done as status AND 100 % together, so this sets both through the same rule the app uses - never set progress to 100 by hand with update_task and hope the status follows.
Schema valid · SHA-256 610c6a3a4fce…
View input schema
{ "type": "object", "properties": { "taskId": { "type": "string", "description": "Task id from list_tasks" } }, "required": [ "taskId" ] }create_gantt
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.
Connections
streamable-http
https://loopgantt.com/api/mcp