{"id":"com.loopgantt/mcp-server","slug":"com-loopgantt-mcp-server","title":"Loopgantt","description":"Create scheduled Gantt charts with critical path from a plain-language plan — no account or key.","version":"1.4.0","publisher":{"kind":"domain","id":"loopgantt.com","label":"loopgantt.com","url":"https://loopgantt.com"},"website":"https://loopgantt.com","repository":"","remotes":[{"type":"streamable-http","url":"https://loopgantt.com/api/mcp"}],"packages":[{"registryType":"npm","registryBaseUrl":"https://registry.npmjs.org","identifier":"@loopgantt/mcp-server","version":"1.4.0","transport":{"type":"stdio"},"environmentVariables":[{"description":"Optional. Enables the account tools create_project / list_projects (https://loopgantt.com/settings/api-keys).","isSecret":true,"name":"LOOPGANTT_API_KEY"}]}],"published":"2026-09-01","updated":"2026-09-01","status":"online","auth":"","latency_ms":1490,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"create_gantt","title":"","description":"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","read_only":false},{"name":"schedule_project","title":"","description":"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.","read_only":false},{"name":"list_templates","title":"","description":"List LoopGantt's industry project templates with task counts and typical durations. Pick one, fetch it with get_template, adapt it, then create_gantt.","read_only":false},{"name":"get_template","title":"","description":"Get one industry template by slug: its task list with durations, ready to adapt and pass to create_gantt.","read_only":false},{"name":"create_project","title":"","description":"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).","read_only":false},{"name":"list_projects","title":"","description":"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.","read_only":false},{"name":"list_tasks","title":"","description":"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","read_only":false},{"name":"update_task","title":"","description":"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.","read_only":false},{"name":"complete_task","title":"","description":"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.","read_only":false},{"name":"create_task","title":"","description":"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.","read_only":false},{"name":"delete_task","title":"","description":"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 a","read_only":false},{"name":"add_comment","title":"","description":"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.","read_only":false},{"name":"list_comments","title":"","description":"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.","read_only":false},{"name":"get_changes","title":"","description":"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","read_only":false},{"name":"list_overdue","title":"","description":"Open tasks whose scheduled end has passed, in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key), most overdue first.","read_only":false},{"name":"list_due_soon","title":"","description":"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.","read_only":false},{"name":"create_meeting","title":"","description":"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:","read_only":false},{"name":"list_meetings","title":"","description":"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.","read_only":false},{"name":"link_external","title":"","description":"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. ","read_only":false},{"name":"list_links","title":"","description":"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.","read_only":false},{"name":"find_by_link","title":"","description":"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.","read_only":false},{"name":"upload_attachment","title":"","description":"Attach a file to a task in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key): a report, export, screenshot or spec the task is about. Send the file as base64 (at most 4 MB). The hosted remote server caps a whole request at 512 KB, so through it a file can be at most about 380 KB; for bigger files use the local server or the REST API upload (POST /api/v1/tasks/{taskI","read_only":false},{"name":"list_attachments","title":"","description":"The files attached to one task in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key), oldest first, with how much of the workspace file storage is used. Each row carries the attachment id that get_attachment and delete_attachment take.","read_only":false},{"name":"get_attachment","title":"","description":"One file on a task in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key): its details and a download link that works for about 5 minutes. Fetch the link right away, or call this again for a fresh one; do not store it.","read_only":false},{"name":"delete_attachment","title":"","description":"Delete one file from a task in the connected LoopGantt ACCOUNT (requires signing in to LoopGantt, or an API key). DESTRUCTIVE and PERMANENT: the file is removed for everyone on the project and cannot be restored. Ask the user before calling, and pass confirm: true only after they agreed; without it nothing is deleted.","read_only":false}],"server_info":{"name":"loopgantt","version":"1.8.0"},"category":"productivity","tags":["project"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-09-01","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/com-loopgantt-mcp-server/"}