# @loopgantt/mcp-server

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

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.4.0
- **Author:** Unknown
- **License:** MIT
- **npm:** @loopgantt/mcp-server
- **Endpoints:** streamable-http https://loopgantt.com/api/mcp
- **Source:** https://github.com/idrjoe/loopgantt-mcp
- **Endpoint health:** reachable (last checked 2026-09-06T16:59:43.939Z, 2 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-09T00:10:44.669Z
- **Version scanned:** 1.4.0
- **CVEs:** none found by OSV at scan time

## Tools

10 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `create_gantt`
- `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 
- `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 LOOPGANTT_API_KEY). For a keyless chart use create_gantt instead.
- `list_projects` — List the projects in the connected LoopGantt account (requires LOOPGANTT_API_KEY).
- `plan_project` — 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
- `goal` — What needs to be delivered
- `deadline` — Target end date (YYYY-MM-DD), if any
- `team_size` — How many people work on it

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp-server\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@loopgantt/mcp-server\"\n      ],\n      \"env\": {\n        \"LOOPGANTT_API_KEY\": \"<YOUR_LOOPGANTT_API_KEY>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `LOOPGANTT_API_KEY` — Loopgantt API Key (optional)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (0 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Moderate blast radius — runs locally and hosted; holds an api key.
- Floor 27, ceiling 27 (tier: moderate)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40loopgantt%2Fmcp-server
- Install plan: https://forgeregistry.com/api/v1/packages/%40loopgantt%2Fmcp-server/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40loopgantt%2Fmcp-server
- HTML page: https://forgeregistry.com/registry/%40loopgantt%2Fmcp-server
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.