petromcp is a small MCP server that lets Claude (or Cursor, or Codex CLI,
or anything else that speaks MCP) read .las well log files directly. If
you have ever tried asking an LLM about a well log you know the workflow
today is to copy-paste curve values into the chat. Petroleum file formats
are binary or semi-structured and the hosts can't open them.
The current release wraps lasio (the established open-source LAS parser)
and exposes five tools: read_las_file, summarize_las_curves,
read_las_curve, compare_well_logs, and convert_units. There is a strict
path allowlist by default, the server makes zero outbound network calls,
and the only data that leaves your machine is whatever the host
application would have sent to its language model anyway.
DLIS, SEG-Y headers, and pump card data are queued for the next releases.
Repo, install instructions, and tool reference are in the README. Feedback
on the QC heuristics from anyone with a petrophysics background would be
particularly welcome. They are defensible defaults but I would rather
have them shaken out than discover problems after a launch demo.
If you have the repo cloned, the server config is:
{
"mcpServers": {
"petromcp": {
"command": "uv",
"args": [
"run",
"--no-sync",
"--project",
"/absolute/path/to/petromcp",
"petromcp",
"serve"
]
}
}
}
Else, you can use {
"mcpServers": {
"petromcp": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/ameyxd/petromcp",
"petromcp",
"serve"
]
}
}
}