P6 EPPM has a documented REST API with OAuth 2.0 that a customer's admin can switch on without Oracle sales. Friction: no developer sandbox, no webhooks, deprecated legacy APIs, and P6 Professional desktop shops mostly exchange XER or XML files.
Oracle Primavera P6 scores B on Supergood's API Report Card. P6 EPPM has a documented REST API with OAuth 2.0 that a customer's admin can switch on without Oracle sales. Friction: no developer sandbox, no webhooks, deprecated legacy APIs, and P6 Professional desktop shops mostly exchange XER or XML files.
Oracle Primavera P6 has a workable official integration path. Most engineering teams can build against it directly. Solid API with minor gaps
Oracle Primavera P6 is the enterprise project scheduling and portfolio management system that grew out of Primavera Systems (founded 1983) and was acquired by Oracle in 2008.
Owners, EPC contractors, engineering firms, utilities, oil and gas, mining, government and infrastructure programs that need contractually mandated CPM schedules. Planners build and update CPM schedules, load resources and costs, set baselines, run progress updates and earned value, and export XER files for owner submissions.
6sense counts 12,374 companies using Primavera P6 with 41.32 percent share of its resource scheduling category, led by the United States (4,408), India (884) and the United Kingdom (722) (https://technographics.6sense.com/resource-scheduling/primavera-p6-cloud-scheduling-software-market-share, retrieved November 2026).
Contract schedules (activities, logic, durations, calendars, baselines), resource and cost loading, progress and earned value, WBS and portfolio hierarchies, and risk registers. P6 schedules often anchor payment, delay claims and owner reporting on capital projects.
Primavera dates to 1983; P6 has carried the name since the mid 2000s under Oracle. Annual numbered releases continue (Release 26 REST API published April 2026).
Stack Overflow developer on P6 EPPM 21.12 found standard project data worked but every Spread REST endpoint was missing from the server. Postman community user could not get the P6 EPPM REST API working in Postman, hitting JSON format errors with the curl examples from Oracle's docs. Full sourced list under Sources below.
Common alternatives include Microsoft Project, Oracle, Asta Powerproject, InEight Schedule, Procore Technologies. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Oracle Primavera P6 is sold both ways: as a vendor-hosted cloud service and as an on-premises installation. Most live deployments are on-premises. Oracle documents both a P6 REST API hosted on Oracle Cloud Infrastructure and an on premises WebLogic configuration guide, and P6 Professional is a Windows desktop client; the on premises lean is inferred.
Oracle Primavera P6 has partial MCP support. No official Oracle MCP server for P6. Community servers exist, including P6 MCP from Buildflows and open source projects that parse XER files or call the P6 EPPM REST API.
Partially. MCP support for Oracle Primavera P6 exists but is incomplete, so what MCP clients like Claude, Cursor, and Codex can reach depends on what the available server covers.