@loopgantt/mcp-server

MCPcommunitylive
v1.4.0UnknownMITUpdated 8d agonpmGitHub

MCP server for LoopGantt — create Gantt charts from Claude Desktop, Cursor or any MCP client, no account needed

Endpoint healthlive
checked 2 days ago · 247ms
100% of the last 2 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
60Downloads/wk
8d agoLast update
Reads these credentials
  • LOOPGANTT_API_KEYAPI keyoptional

    Optional. Enables the account tools create_project / list_projects (https://loopgantt.com/settings/api-keys).

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorUnknown
LicenseMIT
Version1.4.0
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/20
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/5
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
npm Trusted Publishing (Sigstore)+0/5
Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
npm maintainer match+0/5
Earned once your identity is verified above and that login is an npm maintainer of this package
CVE scan · clean+30/30
Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface10 tools · none privileged
Security scan✓ Cleanv1.4.0 · todayHow well does this scan work?
EvalsNone
IndexedAug 31, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

10 tools · none privileged
Statically extracted from the published packagev1.4.0 · 1h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

create_ganttNo description published

This tool published no description. Forge does not invent one.

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 when the user wants a…

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…

No input schema was published for this tool.

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.

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

create_projectCreate a project in the connected LoopGantt ACCOUNT (requires LOOPGANTT_API_KEY). For a keyless chart use create_gantt instead.

Create a project in the connected LoopGantt ACCOUNT (requires LOOPGANTT_API_KEY). For a keyless chart use create_gantt instead.

No input schema was published for this tool.

list_projectsList the projects in the connected LoopGantt account (requires LOOPGANTT_API_KEY).

List the projects in the connected LoopGantt account (requires LOOPGANTT_API_KEY).

No input schema was published for this tool.

plan_projectTurn a goal into a scheduled Gantt chart: draft a work breakdown with realistic durations and dependencies, create it with create_gantt, and present the picture, the critical path and the link.

Turn a goal into a scheduled Gantt chart: draft a work breakdown with realistic durations and dependencies, create it with create_gantt, and present the picture, the critical path and the link.

No input schema was published for this tool.

goalWhat needs to be delivered

What needs to be delivered

No input schema was published for this tool.

deadlineTarget end date (YYYY-MM-DD), if any

Target end date (YYYY-MM-DD), if any

No input schema was published for this tool.

team_sizeHow many people work on it

How many people work on it

No input schema was published for this tool.

9 of 10 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for LoopGantt — create Gantt charts from Claude Desktop, Cursor or any MCP client, no account needed

Keywords
mcpmodel-context-protocolclaudecursorganttgantt-chartproject-managementcritical-pathloopgantt
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-09 — observed resolution, not a publisher declaration.

60 packages resolved · 1 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.