An MCP server for Primavera P6 XER files.
mcp-name: io.github.osama-ata/p6xer-mcp-server A full-featured Model Context Protocol (MCP) server for Primavera P6 XER files, built on PyP6XER. Exposes 13 Tools, 3 Resources, and 2 Prompts so any MCP-compatible AI client (Claude Desktop, Claude Code, Cursor, etc.) can interactively parse, query, and analyze schedule files. ------|-------------| | Parse an XER file — project list, totals, status…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
mcp-name: io.github.osama-ata/p6xer-mcp-server A full-featured Model Context Protocol (MCP) server for Primavera P6 XER files, built on PyP6XER. Exposes 13 Tools, 3 Resources, and 2 Prompts so any MCP-compatible AI client (Claude Desktop, Claude Code, Cursor, etc.) can interactively parse, query, and analyze schedule files. ------|-------------| | Parse an XER file — project list, totals, status breakdowns | | Activities with filters: projectid, projectshortname, status, tasktype | | Critical…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.