PyP6Xer MCP Server
Related Servers
Alternatives to PyP6Xer MCP Server
No user-submitted related servers found.
Related Servers
- 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
- FlicenseNot gradedqualityBmaintenanceEnables natural-language querying of construction project data to analyze schedules, delays, critical activities, risks, and resource bottlenecks, and to generate schedule recovery recommendations.-
- 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
- AlicenseAqualityDmaintenanceMCP server for parsing, querying, and analyzing Primavera P6 XER files with 13 tools, 3 resources, and 2 prompts.1328 PyPI10MIT
- AlicenseAqualityDmaintenanceEnables AI agents to interact with Bentley STAAD.Pro models for tasks like load case definition, data extraction, and property setting, running locally with multi-instance support and no cloud dependency.5MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to analyze log time data from various sources to summarize project health, employee performance, and client status.-
TDQS
Scored across 29 tools
Several tools overlap in purpose: schedule_health_check consolidates float/critical path/open-end data, generate_report bundles slipping activities/health/earned value, and work_package_summary overlaps with wbs_analysis. The descriptions help, but an agent could easily select the wrong analysis or report tool for a given request.
All tools use a consistent pyp6xer_ prefix and snake_case, with clear list/get/search/update/export verbs for operations. A minority of analysis tools use noun-style names such as critical_path, float_analysis, and earned_value, but the overall pattern remains readable and predictable.
At 29 tools, the surface is dense and exceeds the 25-tool threshold. Many narrow analysis/report variants could be consolidated without losing capability, and the large count increases the chance of an agent picking a redundant tool.
The domain is well covered: loading files, listing projects/calendars/resources/activities, searching, detailed activity views, WBS/earned value/float/critical path/quality analyses, snapshot comparison, and update/write/export workflows are all present. The main gap is that modification is limited to activity fields, with no create/delete or relationship/resource editing.