Create scheduled Gantt charts with critical path from a plain-language plan — no account or key.
Connect Remote server
claude mcp add --transport http mcp-server https://loopgantt.com/api/mcp
{
"mcpServers": {
"mcp-server": {
"url": "https://loopgantt.com/api/mcp"
}
}
}
{
"servers": {
"mcp-server": {
"type": "http",
"url": "https://loopgantt.com/api/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://loopgantt.com/api/mcp
Tools 21 found in our last check
create_ganttCreate 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 lin…
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). Use it to answer "what is the critical path?", "when would this finish?", "how much slack does X have?". Use create_gantt w…
list_templatesList LoopGantt's industry project templates with task counts and typical durations. Pick one, fetch it with get_template, adapt it, then create_gantt.
get_templateGet one industry template by slug: its task list with durations, ready to adapt and pass to create_gantt.
create_projectCreate 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 (do…
list_projectsList 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_tasksList 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: pas…
update_taskChange 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…
complete_taskMark 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 sta…
create_taskAdd 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.…
delete_taskDelete 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. The task goe…
add_commentLeave 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…
list_commentsRead 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.
get_changesWhat 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…
list_overdueOpen tasks whose scheduled end has passed, in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key), most overdue first.
list_due_soonOpen 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.
create_meetingBook 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…
list_meetingsMeetings 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.
link_externalAttach 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…
list_linksThe 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.
find_by_linkWhich 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.
Details
| Endpoint | https://loopgantt.com/api/mcp (Streamable HTTP) |
| Package | @loopgantt/[email protected] (NPM, stdio) |
| First published | 1 Sep 2026 |
| Last updated | 1 Sep 2026 |
| Registry name | com.loopgantt/mcp-server |
More productivity servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
