mcp-server

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.

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.

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.

Book a meeting in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key); the key owner is the organizer. Every invitee gets a calendar invitation (.ics, works with Apple, Google, Outlook and any other calendar); members with Google or Outlook sync get it straight in that calendar. Link it to a project (and a task) so the team sees it there. videoProvider picks the call: google_meet, teams or zoom only when the account has that connection, custom = the link you put in location, none = no call.

Create a project in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key). For a keyless chart use create_gantt instead. Pass workflow: "agent_board" for a board a team of agents works on - stages todo, in_progress, blocked, waiting_approval, done (done is the finished stage).

Add one task to an existing project in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key). Put it under a phase with parentId, make it wait for other tasks with dependencies, and hand it to a person with assigneeId or to a bot with agentLabel (e.g. "qa-bot"). Returns the new task id.

Delete one task in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key) - and every task under it when it is a phase. DESTRUCTIVE: ask the user before calling, and pass confirm: true only after they agreed; without it nothing is deleted. It cannot be undone: the task (and every task under it) disappears from the app and cannot be restored; the deleted rows are purged after 30 days.

Which tasks in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key) carry this link — e.g. the task a Jira issue, PR or doc belongs to. Searches only projects the key owner can see.

What changed in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key) since an instant: tasks created, tasks now done and tasks otherwise updated. Built for agents that poll: the first time pass since (e.g. when you last looked); after that pass back BOTH the since and the cursor the previous reply gave you. The cursor resumes exactly after the last task reported, so no task is reported twice and none written in the same millisecond is skipped. Deleted tasks are not reported.

Get one industry template by slug: its task list with durations, ready to adapt and pass to create_gantt.

Attach a link to a task in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key): the GitHub PR, Jira or Linear issue, Google Doc, Figma file or Slack thread the work lives in, so people and other agents can follow it and find the task again with find_by_link. A GitHub PR/issue link also shows its open/merged/closed status when the workspace has the GitHub integration. Linking a URL the task already has just returns it (and updates the title if you give one).

Read the comments on one task in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key), newest first — to pick up a handoff or see what a person decided.

Open tasks scheduled to end within the next N days (today included), in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key), earliest end first.

The links attached to one task in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key): PRs, issues, docs and threads in other apps.

Meetings in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key): the key owner's meetings in a window, a project's meetings in a window, or the upcoming meetings about one task.

Open tasks whose scheduled end has passed, in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key), most overdue first.

List the projects in the connected LoopGantt account (requires signing in to LoopGantt, or an API key), with each project's workflow stages: use one of those stage ids as a task's status.

List tasks in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key), across every project the account can reach, most recently changed first. Use it to answer "what am I working on", to find a task before changing it, or to catch up on what moved: pass updatedSince (ISO timestamp) for "since I last looked". Each row carries the task id that update_task and complete_task take.

List LoopGantt's industry project templates with task counts and typical durations. Pick one, fetch it with get_template, adapt it, then create_gantt.

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.

Change one task in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key). Pass the taskId from list_tasks and only the fields to change. To mark a task done use complete_task — LoopGantt couples status and progress, and complete_task says exactly that. Set agentLabel to claim a task for a bot (null releases it); assigneeId is for a real person.