Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
6,000+ web scrapers for your AI agent, start free logo6,000+ web scrapers for your AI agent, start free

Apify gives your agent live web data: 6,000+ prebuilt scrapers and actors, MCP-ready. Sign up free with $5 in usage credits.

Try Apify free
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 48,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

Real-time oil, gas, and commodity prices. Brent, WTI, natural gas, diesel & more.

README.md

OilPriceAPI MCP Server

Give compatible AI clients source-timestamped oil, gas, LNG, carbon, fuel, and related energy data through MCP. No API key is needed to try the limited demo.

![npm](https://www.npmjs.com/package/oilpriceapi-mcp) ![Downloads](https://www.npmjs.com/package/oilpriceapi-mcp) ![license](LICENSE)

Get a Free API Key · Documentation · API Explorer · Pricing

Backed by OilPriceAPI, a normalized REST API for energy dashboards, fleet and logistics tools, maritime workflows, and market research.

Features

  • Reviewed product facts — a keyless read-only tool and stable resource for offer, freshness, authentication, catalog, entitlement, and data-rights questions
  • Data and workflow tools — latest values, history, futures, marine fuels, fuel surcharges, energy intelligence, alerts, market briefs, and persistent watches
  • Resources — the reviewed product contract plus subscribable price snapshots
  • Prompts — analyst templates for briefings, spread analysis, gas markets, diesel costs, and supply analysis
  • Natural language — ask for "brent oil" or "natural gas", not codes
  • Broad catalog — oil, gas, coal, refined products, metals, forex, bunker fuels, state diesel, and selected energy-intelligence datasets; access varies by plan and account
  • Smart errors — unrecognized commodities get suggestions, not silent fallbacks

Quick Start

npx oilpriceapi-mcp

The default scope is read-only. Account mutations are not listed and direct mutation calls are rejected unless write scope is explicitly enabled:

npx oilpriceapi-mcp --scope write

Inspect the package without opening an MCP stdio session:

npx oilpriceapi-mcp --version
npx oilpriceapi-mcp --list-tools
npx oilpriceapi-mcp --list-tools --json --profile core
npx oilpriceapi-mcp doctor --demo
npx oilpriceapi-mcp doctor
npx oilpriceapi-mcp --capabilities --json
npx oilpriceapi-mcp --config claude-code
npx oilpriceapi-mcp --config vscode

--config generates client-native, copy/paste-valid JSON for claude-desktop, claude-code, cursor, vscode, cline, or windsurf. It never reads or prints the configured API key. Claude Code, VS Code, and Windsurf outputs use their supported environment or secure-input references; Claude Desktop, Cursor, and Cline use an explicit local replacement marker. Add --demo to omit API-key configuration entirely. Scope, profile, and category options are preserved in the generated server arguments.

What can your agent get?

Example commodity codes:

| Code | What it is | Typical agent use | | ----------------- | ------------------------ | ------------------------------ | | BRENT_CRUDE_USD | Brent crude (global) | market briefings, dashboards | | WTI_USD | WTI crude (US) | trading context, macro models | | NATURAL_GAS_USD | Henry Hub natural gas | energy analytics | | DUTCH_TTF_EUR | TTF gas (Europe) | European energy, LNG analysis | | JKM_LNG_USD | JKM LNG (Asia) | LNG trading & shipping | | EU_CARBON_EUR | EU ETS carbon allowances | CBAM, maritime compliance, ESG | | DIESEL_USD | Diesel (Gulf Coast) | fleet & fuel-surcharge math | | JET_FUEL_USD | Jet fuel | aviation ops | | VLSFO_USD | Marine bunker fuel | voyage costing | | GOLD_USD | Gold | macro & portfolio context |

Installation

Try it without an API key

The server works out of the box in keyless demo mode — just omit OILPRICEAPI_KEY from the configs below. The price tools (opa_get_price, opa_compare_prices, opa_list_commodities, opa_market_overview) serve latest available values for a limited demo commodity set, and every other data tool explains its account requirements. Demo responses are marked with a footer. For the broader account-enabled catalog, history, futures, and alerts, get a free API key and add it to your config.

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "oilpriceapi": {
      "command": "npx",
      "args": ["-y", "oilpriceapi-mcp"],
      "env": {
        "OILPRICEAPI_KEY": "your-api-key-here"
      }
    }
  }
}

Claude Code

Add to your project's .mcp.json:

{
  "mcpServers": {
    "oilpriceapi": {
      "command": "npx",
      "args": ["-y", "oilpriceapi-mcp"],
      "env": {
        "OILPRICEAPI_KEY": "your-api-key-here"
      }
    }
  }
}

Cursor

Add to .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "oilpriceapi": {
      "command": "npx",
      "args": ["-y", "oilpriceapi-mcp"],
      "env": {
        "OILPRICEAPI_KEY": "your-api-key-here"
      }
    }
  }
}

VS Code + Cline

Add to .vscode/mcp.json:

{
  "servers": {
    "oilpriceapi": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "oilpriceapi-mcp"],
      "env": {
        "OILPRICEAPI_KEY": "your-api-key-here"
      }
    }
  }
}

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "oilpriceapi": {
      "command": "npx",
      "args": ["-y", "oilpriceapi-mcp"],
      "env": {
        "OILPRICEAPI_KEY": "your-api-key-here"
      }
    }
  }
}

Global Install

npm install -g oilpriceapi-mcp

Environment Variables

| Variable | Required | Description | | ---------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | OILPRICEAPI_KEY | No | API key from oilpriceapi.com/signup. After the core trial, the Free plan includes 200 requests/month. Dataset access and limits vary by plan and entitlement. Without a key, the server uses the limited demo. | | OILPRICEAPI_BASE_URL | No | Override API base URL (for staging/testing). Default: https://api.oilpriceapi.com | | OILPRICEAPI_MCP_SCOPE | No | read (default) hides and blocks create/delete tools. Set write only when account mutations are intended. | | OILPRICEAPI_MCP_PROFILE | No | Stable inventory profile: all (default), core, market, or automation. | | OILPRICEAPI_MCP_CATEGORIES | No | Comma-separated category allowlist (core, market, automation). Overrides the selected profile. |

Tool Scope and Profiles

read scope includes all non-mutating tools, including alert history, subscription listing, and subscription event polling. The four create/delete tools require --scope write or OILPRICEAPI_MCP_SCOPE=write. Unknown scope, profile, or category values fail closed before stdio starts.

Profiles reduce tool overload without replacing first-class MCP actions:

| Profile | Included categories | | ------------ | ------------------------ | | all | core, market, automation | | core | core | | market | core, market | | automation | core, automation |

For example, a read-only price and product-facts server can use:

{
  "command": "npx",
  "args": ["-y", "oilpriceapi-mcp", "--scope", "read", "--profile", "core"]
}

Doctor and Capability Contract

doctor checks the Node runtime, package entry point, API reachability, key validity, current plan, and reported feature gates. doctor --demo performs a bounded keyless request. Failures distinguish missing configuration, 401, 402, 403, 429, timeout, DNS/TLS, and upstream 5xx responses. The API key is never printed.

Every package includes build/capabilities.json. It is generated from the same SDK registry used by tools/list and records the package/version/source commit, minimum Node version, scopes, profiles, exact inventories, per-tool annotations, key/entitlement requirements, resources, commands, and support URLs. Website and docs consumers should pin a package version, validate schemaVersion and sourceCommit, and update the artifact only through an explicit dependency upgrade. They should not scrape CLI prose or hard-code tool counts.

Tools

All tools are prefixed with opa_ to avoid name collisions when multiple MCP servers are loaded.

| Tool | Description | | ------------------------- | ----------------------------------------------------------------------------------------------- | | opa_get_product_facts | Reviewed product, offer, freshness, auth, integration, entitlement, and data-rights contract | | opa_get_price | Current spot price for a single commodity | | opa_market_overview | All commodity prices in one call, grouped by category | | opa_compare_prices | Side-by-side comparison of 2-5 commodities with spread | | opa_list_commodities | Full commodity catalog (fetched live from API) | | opa_get_history | Historical prices with high/low/avg/change (day/week/month/year) | | opa_get_futures | Front-month futures (Brent BZ, WTI CL, ICE Gasoil, TTF, JKM, EUA) | | opa_get_futures_curve | Full forward curve with contango/backwardation analysis | | opa_get_marine_fuels | Bunker fuel prices by port and fuel type (VLSFO/MGO/IFO380) | | opa_get_rig_counts | Baker Hughes US rig count with week-over-week change | | opa_get_drilling | Drilling snapshot: rig counts, frac spreads, 30-day permits, DUCs | | opa_get_diesel_by_state | AAA retail diesel price for any US state (50 states + DC) | | opa_get_fuel_surcharge | LTL and parcel carrier fuel surcharge percentages with effective dates and source provenance | | opa_get_storage | Cushing and SPR oil storage/inventory levels | | opa_get_opec_production | OPEC country-level production data | | opa_get_forecasts | EIA STEO energy price forecasts | | opa_get_oil_inventories | EIA weekly petroleum stocks (latest/summary/by_product) | | opa_get_well_permits | US well drilling permits (latest/by_state/by_operator) | | opa_search_well_permits | State-scoped permit search by county/operator/date with measured freshness gate | | opa_lookup_well | API-number lookup with promoted lifecycle and exact monthly production when available | | opa_get_well_activity | Recent permit counts/top operators/trends with explicit state-health warnings | | opa_get_well_production | US well production — beta coverage (summary/states/state/well/top_producers/cycle_time/cohorts) | | opa_get_spread | Refining/trading spreads (crack, basis, margin) |

Price Alert Tools (authenticated)

These tools create and manage persistent price alerts tied to your OilPriceAPI account, so they require an API key (OILPRICEAPI_KEY). The alert engine evaluates eligible source updates and notifies you (by email, plus webhook if you provide one) when a condition is met.

| Tool | Description | | ------------------------ | ---------------------------------------------------------------------------- | | opa_create_price_alert | Create a persistent alert (commodity, operator, threshold, optional webhook) | | opa_list_price_alerts | List all alerts on the account | | opa_delete_price_alert | Permanently delete an alert by id | | opa_get_alert_triggers | Recent alert trigger activity (optionally filtered by since) |

Market Brief & Subscription Tools (authenticated)

The market brief gives a multi-commodity snapshot in one call. Subscriptions ("watches") are persistent, recurring snapshots tied to your account — the API records an event every interval, and the agent polls for new events via a per-user cursor (events are polled, not pushed — there is no always-on connection). These require an API key (OILPRICEAPI_KEY). A subscription differs from an alert: a watch always emits an event each interval (a running log), whereas an alert fires only on a threshold crossing. Per-tier limits apply (free: 1 watch, 3 codes, 1h minimum interval); the API returns the exact limit if exceeded.

| Tool | Description | | ------------------------------- | ------------------------------------------------------------------------------------- | | opa_get_market_brief | Multi-commodity brief: prices, 24h changes, 1m forecasts, spreads, optional narrative | | opa_create_price_subscription | Create a persistent recurring watch (codes, interval like 5m/1h/daily) | | opa_list_subscriptions | List all subscriptions on the account | | opa_delete_subscription | Permanently delete a subscription by id | | opa_get_subscription_events | Poll for new watch events since a cursor (since); returns snapshots + deltas |

Example Questions

"What's the current Brent oil price?"
"Compare Brent and WTI crude"
"Show me oil prices for the past month"
"What's diesel cost in California vs Texas?"
"Give me a market overview of refined products"
"What's the Brent futures curve look like?"
"How many oil rigs are active in the US?"
"What are OPEC production levels?"
"What are bunker fuel prices in Singapore?"
"Show me Cushing storage levels"
"What were the latest EIA crude oil inventories?"
"How many well permits were issued in Texas?"
"What's the current 3-2-1 crack spread?"
"What's the UPS ground fuel surcharge?"
"Show me the ICE Gasoil futures curve"

Resources

Subscribable price data (JSON):

| Resource | URI | Description | | ------------- | ----------------------------- | ------------------------------------------- | | Product Facts | oilpriceapi://product-facts | Reviewed, versioned public product contract | | Brent Crude | price://brent | Global benchmark crude oil price | | WTI Crude | price://wti | US benchmark crude oil price | | Natural Gas | price://natural-gas | US Henry Hub natural gas price | | Diesel | price://diesel | US national average diesel price | | All Prices | price://all | All tracked commodity prices |

Product Facts and Model Knowledge

opa_get_product_facts and oilpriceapi://product-facts improve accuracy for a connected MCP session. They do not retrain a model or update its general knowledge. The server prefers the canonical keyless contract, uses a bounded cache, and labels any checksum-verified package fallback with source and warning metadata.

Prompts

Pre-built analyst templates:

| Prompt | Description | | ---------------------- | --------------------------------------------------------- | | daily-briefing | Energy market daily briefing with key prices and movers | | brent-wti-spread | Analyze the Brent-WTI crude oil spread | | gas-market-analysis | Compare US vs European natural gas markets | | commodity-report | Detailed report on a specific commodity (parameterized) | | diesel-cost-analysis | Compare diesel prices across US states for fleet planning | | supply-analysis | Analyze supply using OPEC production, rig counts, storage |

Natural Language Support

| You say | We understand | | --------------------------- | --------------- | | "brent oil", "brent crude" | BRENT_CRUDE_USD | | "wti", "us oil" | WTI_USD | | "natural gas", "henry hub" | NATURAL_GAS_USD | | "european gas", "ttf" | DUTCH_TTF_EUR | | "diesel" | DIESEL_USD | | "gold" | GOLD_USD | | "jet fuel", "aviation fuel" | JET_FUEL_USD | | "carbon", "carbon credits" | EU_CARBON_EUR |

Development

npm install
npm run build
npm test
OILPRICEAPI_KEY=your-key node build/index.js

Breaking Changes in v3.0.0

  • The default tool scope is now read-only. Create/delete alert and subscription

tools require explicit --scope write or OILPRICEAPI_MCP_SCOPE=write.

  • Invalid scope/profile/category configuration now fails before MCP stdio starts.
  • Use --list-tools --json or --capabilities --json instead of relying on a

hard-coded inventory.

Breaking Changes in v2.0.0

  • All tool names now use opa_ prefix (e.g., get_commodity_price -> opa_get_price)
  • Unrecognized commodity names now return an error with suggestions instead of silently defaulting to Brent
  • list_commodities now fetches live from the API (falls back to static list if unavailable)

The whole OilPriceAPI toolbox

Same data, every stack:

| Tool | Install | | ------------------------------------------------------------------------------- | ---------------------------------------------- | | Python SDK | pip install oilpriceapi | | Node/TypeScript SDK | npm install oilpriceapi | | PHP SDK | composer require oilpriceapi/oilpriceapi | | Go SDK | go get github.com/OilpriceAPI/oilpriceapi-go | | WordPress plugin | no-code price widgets |

Explore the API

Privacy Policy

This MCP server runs locally on your machine and only communicates with the OilPriceAPI service:

  • What is sent: tool requests are translated into HTTPS calls to api.oilpriceapi.com (commodity codes, query parameters such as time period or state, carrier slugs and service-level inputs for fuel surcharges, and — for alert/subscription tools — the alert parameters you specify), authenticated with your API key. No conversation content is transmitted — only the structured tool inputs above.
  • API key storage: your key is stored locally in your MCP client's configuration (or the OILPRICEAPI_KEY environment variable). It is sent only to api.oilpriceapi.com as an Authorization header.
  • Logging and demand telemetry: each tool emits a local structured hit/miss event to stderr and attributes its API request with the tool name plus a deliberately lossy argument shape. Commodity codes, intervals, state codes, and bounded numeric controls may be retained; free text, prompts, names, IDs, API well numbers, coordinates, and thresholds are reduced to provided. API request logging follows the OilPriceAPI Privacy Policy.
  • Third parties: no data is shared with third parties beyond what that policy describes.
  • Demo mode: without an API key, price tools call the keyless demo endpoint on the same host; no key or account data is involved.

Questions: support@oilpriceapi.com

Pricing Boundary (HTTP 402)

Where the free/paid line sits for this server (#10):

  • Always open: the MCP server itself (MIT), setup, docs, discovery (tool listing), and keyless demo mode for low-volume evaluation.
  • Free API key: the core trial includes 10,000 requests over 7 days with no credit card; afterward the Free plan includes 200 requests per month. Dataset access varies by plan and entitlement.
  • Behind the paywall: high-volume usage and premium datasets (futures, energy intelligence, well permits/production, alerts at scale). When a request crosses that boundary the API returns a standard HTTP 402/403/429 with the exact limit or feature gate in the body, and this server surfaces that message plus an upgrade link — agents get a machine-readable stop, never a silent failure.
  • x402 protocol: per-request crypto micropayments via the x402 protocol are not currently supported — payment is by account plan (Stripe), authenticated with your API key.

License

MIT

Links

Also Available As

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Other servers.