@loopgantt/mcp-server
Related Servers
Alternatives to @loopgantt/mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceAn OAuth-protected MCP server that converts project descriptions into realistic schedules, handling dependencies, resource leveling, critical path analysis, and generating shareable charts (HTML, SVG, PNG, JSON, CSV).-
- AlicenseNot gradedqualityDmaintenanceEnables collaborative project planning by connecting an MCP-capable chat app to a generative AI that manages tasks and dependencies, with a live web UI for visualization.1GPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP-capable agents to create, edit, analyze, and export desktop Microsoft Project schedules through COM automation, covering tasks, WBS, dependencies, resources, calendars, baselines, earned value, and critical-path reporting.MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI clients to query, analyze, and mutate Oracle Primavera P6 schedules from XER files or live P6 EPPM, with tools for critical path, DCMA compliance, earned value, resources, baselines, and exports.31 PyPI1MIT
- AlicenseBqualityCmaintenanceEnables project and program managers to generate plan, forecast, risk, capacity, and flow reports from Jira boards inside MCP-capable AI assistants, including Gantt charts, milestones, dependency maps, workload heatmaps, Monte Carlo finish-date forecasts, and exports. It reads Jira read-only and returns deterministic calculations, charts, and files through natural-language chat.10MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to build and calculate critical-path project plans through tools, including resource leveling, vacation and holiday calendars, what-if scenario comparison and Monte Carlo schedule risk simulation. Projects are read from and written as plain JSON files.MIT
TDQS
Scored across 4 tools
list_templates and get_template are clearly a list/detail pair, while create_gantt and schedule_project share the same input shape and both surface dates and critical path. The descriptions clearly distinguish them by output and intent—create_gantt for a viewable chart, schedule_project for pure computation—so an agent can disambiguate with careful reading.
All four tools follow a consistent verb_noun snake_case pattern: list_templates, get_template, create_gantt, schedule_project. There are no mixed conventions or stylistic deviations.
Four tools form a tight, well-scoped set: template discovery, template retrieval, chart creation, and schedule computation each have exactly one tool. Nothing feels redundant or missing at the current scope.
The stated template-to-Gantt workflow is fully covered: list templates, fetch one, create a chart, or compute a schedule. There is no management layer for updating or deleting previously created charts, but the returned link handles viewing/exporting/saving, making this a minor gap rather than a critical one.