resinsight-mcp

resinsight-mcp connects an MCP-enabled agent to ResInsight workflows. MCP is the Model Context Protocol for tool access. Through a configured host, an agent can manage sessions and projects, inspect objects, change views, and examine fresh native images.

The project builds an agent interface for ResInsight-based modeling, simulation, and result analysis. The first-release plan targets macOS and OPM Flow with explicit model and physics limits.

Start with your connection

Use the connection guide to connect an MCP client and discover its available tools. The supplied launcher provides workspace tools and optional ResInsight session configuration. Its model configuration enables supported FIELD imports and constrained model creation. Its OPM workflow configuration adds native wells, bounded Flow jobs, verified results, comparisons, and fresh images.

The operation map records the current tools, required configuration, evidence, and remaining integration work.

Choose a task

The tutorials use implemented tools and identify the setup each task requires.

• Manage sessions and projects: open, save, reopen, and find the objects your agent will use.
• Create and prepare models: import or generate FIELD inputs, inspect them, and clone immutable revisions.
• Run the FIELD workflow: publish native completions, run a baseline and changed scenario, compare results, and restore project bindings.
• Inspect and change views: compare properties and report times with fixed legends, filters, cameras, and native images.
• Monitor local jobs: inspect progress, request cancellation, and recover the same job identity after reconnecting.

The session reference, view reference, and job reference describe outcomes and supported limits. The model guide describes the constrained specification, fixed physics template, and Python interface. The well guide describes native well edits and separate publication of immutable simulator schedules. The OPM guide and result guide explain runtime limits, accepted outputs, exact result identity, and numerical comparisons.

Know where information goes

ResInsight control, rendering, and MCP tools can run locally while the client uses a remote model API. Depending on the client configuration, prompts, tool results, metadata, and images can reach the model provider. The product assumes that users have appropriate provider data sharing agreements. The data boundary explains this configuration.

Develop and verify

The development guide covers the architecture, shared contracts, storage, and package ownership behind the agent tools. Its acceptance records distinguish service tests, native application trials, and model-visible image evidence. The local setup guide explains installation, tests, and documentation preview. The contribution policy explains how to propose a change.