loopgantt.com MCP server
by loopgantt.com MCP server, indexed and not reviewed
HostedLocalvendor's own
Not reviewed
No score, grade or rank. This listing is facts from the official MCP registry and our own checks, and it stays out of the rankings until the panel reviews it.
Create scheduled Gantt charts with critical path from a plain-language plan — no account or key.
Facts
- MCP registry
com.loopgantt/mcp-server· 1.4.0- Endpoint
https://loopgantt.com/api/mcp- Packages
npm@loopgantt/mcp-server stdio- Website
- loopgantt.com
- npm / week
- 65
- Registry entry
- updated 1 Sep 2026
From the official MCP registry, the package registries and our own checks. JSON · Markdown
Why it's listed
- It's published in the registry under loopgantt.com, a namespace the registry only gives to whoever proves they control that domain.
Being indexed says nothing about quality, and nobody can pay for it. Is this yours? Ask for a review.
Tools it lists 25 · about 6,313 tokens of context · checked 19 hours ago
| Tool | What it does | Hint |
|---|---|---|
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… | |
schedule_project | 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… | |
list_templates | List LoopGantt's industry project templates with task counts and typical durations. Pick one, fetch it with get_template, adapt it, then create_gantt. | |
get_template | Get one industry template by slug: its task list with durations, ready to adapt and pass to create_gantt. | |
create_project | 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 -… | |
list_projects | 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 | 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… | |
update_task | 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… | |
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… | |
create_task | 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… | |
delete_task | 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… | |
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… | |
list_comments | 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. | |
get_changes | 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… | |
list_overdue | 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_due_soon | 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. | |
create_meeting | 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… | |
list_meetings | 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. | |
link_external | 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… | |
list_links | 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. | |
find_by_link | 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. | |
upload_attachment | 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… | |
list_attachments | 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… | |
get_attachment | 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… | |
delete_attachment | 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… |
What https://loopgantt.com/api/mcp answered to tools/list, asked without credentials over MCP 2025-11-25. The token figure is the size of the list as sent, divided by four; a model sees about that much before it calls anything. Full definitions, input schemas included, are in the listing's JSON under mcpTools.
How its tools read to an agent 0 errors · 31 warnings · 1 note
- warnTC11create_gantt2 parameters without a description: tasks, tasks[].description
- warnTC11create_meeting2 parameters without a description: notes, title
- warnTC11create_projectnone of its 5 parameters has a description
- warnTC11create_task4 parameters without a description: description, isMilestone, name, priority
- warnTC11schedule_project2 parameters without a description: tasks, tasks[].description
- warnTC11update_task4 parameters without a description: description, isMilestone, name, priority
- warnTC16add_commentno readOnlyHint or destructiveHint
- warnTC16complete_taskno readOnlyHint or destructiveHint
- warnTC16create_ganttno readOnlyHint or destructiveHint
- warnTC16create_meetingno readOnlyHint or destructiveHint
- warnTC16create_projectno readOnlyHint or destructiveHint
- warnTC16create_taskno readOnlyHint or destructiveHint
- warnTC16delete_attachmentno readOnlyHint or destructiveHint
- warnTC16delete_taskno readOnlyHint or destructiveHint
- warnTC16find_by_linkno readOnlyHint or destructiveHint
- warnTC16get_attachmentno readOnlyHint or destructiveHint
- warnTC16get_changesno readOnlyHint or destructiveHint
- warnTC16get_templateno readOnlyHint or destructiveHint
- warnTC16link_externalno readOnlyHint or destructiveHint
- warnTC16list_attachmentsno readOnlyHint or destructiveHint
- warnTC16list_commentsno readOnlyHint or destructiveHint
- warnTC16list_due_soonno readOnlyHint or destructiveHint
- warnTC16list_linksno readOnlyHint or destructiveHint
- warnTC16list_meetingsno readOnlyHint or destructiveHint
The first 24 of 32; every finding is in the listing's JSON under mcpTools.check.
The checks from /check and anchor check, run each day on the list above: about 6,313 tokens of definitions. Not part of the score yet. Check your own server.