A controlled route into desktop geoscience
The public MCP server exposes 41 tools without depending on the Ocean SDK. Its documented toolbox includes 32 tools that work on project or export files without launching Petrel. Other routes call saved Petrel workflows or use bounded GUI procedures when required.
The engineering aim is to make each operation inspectable: explicit inputs, validation artifacts, checksums and a result audit. Tools that can launch Petrel default to dry runs and require explicit execution. Unresolved layouts or failed preflights return their limits instead of guessing.