@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 gradedqualityBmaintenanceEnables 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 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.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that enables LLMs to read and analyze Microsoft Project schedules, including critical path, resources, and advanced construction planning layers (AWP and LPS) for work packages and Lean planning.MIT
- FlicenseNot gradedqualityBmaintenanceEnables autonomous scheduling of creator content deliverable calendars and embargo wave campaigns through natural language, integrating with MCP-compliant clients for deterministic, zero-dependency execution.8-
- AlicenseBqualityBmaintenanceFull natural language control over Google Calendar, Drive, Gmail, Docs, Sheets, Slides, Forms, Tasks, Contacts, and Chat through all MCP clients, AI assistants and developer tools.124MIT
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.