Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
Description from the maker (original English)
Local-first MCP server: read LAS well logs and DLIS files from your own disk.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"petromcp": {
"command": "uvx",
"args": [
"petroleum-mcp"
]
}
}
}Run this in your terminal
claude mcp add petromcp -- uvx petroleum-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"petromcp": {
"command": "uvx",
"args": [
"petroleum-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"petromcp": {
"type": "stdio",
"command": "uvx",
"args": [
"petroleum-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account ameyxd, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.8.1) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Agent-Native Google Calendar - manage events, sync, and public booking
Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Read well logs with Claude without the data ever leaving your machine.
petromcp is an MCP server for petroleum data formats, built for teams whose files legally cannot be uploaded to a cloud service. No telemetry, no phone-home, no automatic updates, and a default-deny path allowlist that refuses to open anything you have not explicitly permitted. LAS today; DLIS, SEG-Y, and pump cards next.
If you can upload your data somewhere, you have more options than this. If you can't, this was written for you.
LLM hosts cannot read binary or semi-structured petroleum formats. petromcp wraps the established open-source parsers — lasio and dlisio today, with segyio queued for a later slice — and exposes them as MCP tools, so you can have a conversation with your data instead of copy-pasting curve values into chat.
Not a posture. Four things you can verify in the source:
openWorldHint: false and readOnlyHint: true, so your host can verify that claim rather than take it.downsampled and original_count, so a 20,000-point log cannot silently dump into a context window.The threat model, and what does *not* count as a vulnerability, are in SECURITY.md. Read docs/DATA_PRIVACY.md before pointing this at real data — it is authoritative, and if the code contradicts it the code is the bug.
Requires Python 3.10+ and uv.
Add petromcp to your MCP host's config — no clone, no build:
{
"mcpServers": { "petromcp": { "command": "uvx", "args": ["petroleum-mcp", "serve"] } } }
On macOS that file is ~/Library/Application Support/Claude/claude_desktop_config.json. Restart the host afterwards. macOS notes and troubleshooting: docs/INSTALL.md.
To work on petromcp rather than just use it:
git clone https://github.com/ameyxd/petromcp cd petromcp make setup make install-claude
By default petromcp can read nothing. Tell it which directories are fair game:
uvx petroleum-mcp config init uvx petroleum-mcp config add-path ~/petroleum/wells
Or, if you want to try it without your own data, generate the synthetic sample from a checkout and allowlist that:
make generate uvx petroleum-mcp config add-path "$(pwd)/examples/sample_data"
Restart your MCP host after editing the allowlist — it is read once at startup.
Open a new conversation and ask, in plain language:
What's wrong with this well log? /path/to/well.las Compare these two wells: /path/to/A.las and /path/to/B.las Convert 1500 psi to kPa.
Claude picks the right tool, reads the file through petromcp, and answers.
Worked examples, with real tool output rather than prose:
Every value in those documents is generated by calling the tools; CI fails if they drift.
| 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 |
qc_a_well_log prompt | Walks Claude through a standard QC pass |
Every tool is read-only and opens no network connection, and declares that in its MCP annotations. Full reference: docs/TOOLS_REFERENCE.md.
DLIS files hold several logging runs, each with several frames, so a channel name is unique only within a frame. read_dlis_channel refuses an ambiguous name and lists the candidates rather than guessing, because the values differ.
SEG-Y and pump card support land in subsequent releases.
v0.7 ships the LAS and DLIS slices, a comparison tool, a units utility, and config-management CLI subcommands. The remaining formats are tracked in SPEC_petromcp.md. The non-goals list there is real; read it before filing feature requests.
Release history: CHANGELOG.md. Security policy and threat model: SECURITY.md.
MIT.
mcp-name: io.github.ameyxd/petromcp
Built by Amey Ambade. I write about AI systems in industries where the data can't leave the building, at writing.heyamey.com.