Local-first MCP server: read LAS well logs and DLIS files from your own disk.
Connect Petromcp to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Local-first MCP server: read LAS well logs and DLIS files from your own disk. The petromcp mcp server is what makes that connection.
Read well logs with Claude without the data ever leaving your machine.
petroleum-mcp on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
read_las_file — Header-level summary of a LAS filesummarize_las_curves — Per-curve min, max, mean, stddev, gap percentageread_las_curve — Depths and values for one curve, with sampling capcompare_well_logs — Common curves, depth overlap, unit consistency, flagsconvert_units — ft<->m, psi<->kPa, psi<->bar, bbl<->m3, degF<->degC, mD<->m2list_supported_units — Every convertible pair with its physical quantityread_dlis_file — DLIS structure: logical files, frames, index typeslist_dlis_channels — Every DLIS channel with its frame, units, and lengthread_dlis_channel — One DLIS channel's values, with a sampling capAmong the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Petromcp's toolset — read_las_file, summarize_las_curves, read_las_curve and 6 more — is a fair guide to whether it matches your workflow. It is maintained by ameyxd; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| read_las_file | Header-level summary of a LAS file |
| summarize_las_curves | Per-curve min, max, mean, stddev, gap percentage |
| read_las_curve | Depths and values for one curve, with sampling cap |
| compare_well_logs | Common curves, depth overlap, unit consistency, flags |
| convert_units | ft<->m, psi<->kPa, psi<->bar, bbl<->m3, degF<->degC, mD<->m2 |
| list_supported_units | Every convertible pair with its physical quantity |
| read_dlis_file | DLIS structure: logical files, frames, index types |
| list_dlis_channels | Every DLIS channel with its frame, units, and length |
| read_dlis_channel | One DLIS channel's values, with a sampling cap |
{
"mcpServers": {
"petromcp": {
"command": "uvx",
"args": ["petroleum-mcp", "serve"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.