⚡ Energy & Commodity MCP — Futures, FX, Rates, Crypto

A live Model Context Protocol (MCP) server that gives your AI agent direct, on-demand access to energy and commodity market data — futures, COT positioning, FX, rates, crypto, and vessel flows — through a single hosted endpoint. Connect once from Claude Desktop, Cursor, Windsurf, Cline, or n8n and let the model pull the numbers itself.

Large language models are excellent at reasoning about markets and terrible at knowing today's numbers. The Energy & Commodity MCP closes that gap. Instead of copy-pasting quotes into a prompt, this MCP server exposes a focused toolbox of energy- and commodity-market data sources the model can call autonomously, mid-conversation, whenever it needs a live figure. Ask "is crude positioning stretched and how does that line up with the dollar?" and the agent calls the futures, COT, and FX tools, then reasons over the results — no tab-switching, no glue code. It is a hosted, always-on endpoint: nothing to install beyond pointing your MCP client at the URL. It runs on Apify's infrastructure and bills per tool call.

Tools

• Futures — current prices and contract data for energy and commodity futures (crude, natural gas, refined products, metals, ags), grounding any "where is X trading" question in a live quote.
• COT (Commitments of Traders) — positioning showing how commercial hedgers, managed money, and other trader categories lean in a given futures market — the canonical read on crowded vs stretched positioning.
• FX — spot rates for the currency pairs that drive commodity pricing (the dollar above all, plus commodity-linked crosses), so the model can connect a dollar move to a commodity move.
• Rates — benchmark interest-rate levels for the macro backdrop that shapes carry, storage economics, and risk appetite.
• Crypto — prices for major crypto assets, for desks that treat digital assets as part of the broader macro/commodity-adjacent risk picture.
• Vessels — vessel and shipping-flow data relevant to physical commodity movement, a window into the seaborne logistics connecting supply and demand.

Each tool returns structured data the model reads and reasons over directly. Because the agent decides which tools to call, a single natural-language question can fan out across futures, COT, FX, and vessels in one turn.

Connect

The server speaks the Model Context Protocol over a hosted endpoint:

https://nexgendata--energy-commodity-mcp.apify.actor/mcp

Add it to any MCP-compatible client:

• Claude Desktop — add the server to your claude_desktop_config.json MCP block with the URL above and your Apify token, then restart. The tools appear in the tray and Claude calls them when a question needs live data.
• Cursor — add the MCP server under Settings → MCP / tools with the same URL and token.
• Windsurf — register the endpoint in Windsurf's MCP configuration; Cascade can invoke the tools inline.
• Cline — add the server URL to Cline's MCP settings in VS Code.
• n8n — use an MCP client node pointed at the endpoint to wire commodity-data tool calls into automated workflows.

Authentication is via your Apify token — the same token you use for any Apify actor. Because it's hosted, there's no local process to run or keep alive.

Use cases

• Conversational commodity research — ask in plain language and let the agent call futures, COT, and FX tools and synthesize an answer.
• Agentic morning briefs — an n8n or Claude workflow calls the tools each morning and drafts a desk note covering price moves, positioning, FX, and rates.
• Cross-asset reasoning — combine futures prices, rate levels, and FX in one pass to explain a commodity move in macro context.
• Positioning monitoring — use the COT tool to track approach to crowded extremes and flag positioning/price divergence.
• Physical-flow context — layer vessel/shipping data onto a price discussion for energy and bulk-commodity analysis.
• Crypto-as-macro tie-in — fold digital-asset moves into the broader risk narrative for desks that watch crypto as a risk-appetite signal.
• Ad-hoc analyst Q&A — the model fetches the number itself, so the analyst stays in the flow of the question.

Pricing

This MCP server bills on Apify's pay-per-event model, per tool call — you pay only when the agent actually invokes a tool, not for idle connection time:

• $0.10 per tool call (one charge each time the model calls a tool)
• A negligible start cost per session (sub-cent at typical memory)

No subscription, no seat licence, no minimum.

Cost worked example

• A cross-asset question triggering 3 tool calls (futures + COT + FX) → 3 × $0.10 = $0.30
• A scheduled morning brief making ~6 tool calls → $0.60/day, ~$13/month
• A heavy research session of 50 tool calls → $5.00

An idle connection costs nothing — you pay only when the agent reaches for data, so cost scales with how much the model actually queries.

FAQ

Q: What is an MCP server and why use one?

A: The Model Context Protocol is an open standard that lets AI clients (Claude Desktop, Cursor, Windsurf, Cline, n8n, and others) call external tools during a conversation. The model decides when to call them. This server's tools deliver live energy/commodity data so the model grounds answers in real numbers instead of guessing.

Q: Do I have to install anything?

A: No. It's a hosted endpoint — add the URL and your Apify token to your MCP client's config; there's no local server to install, run, or maintain.

Q: Which clients are supported?

A: Any MCP-compatible client. We document Claude Desktop, Cursor, Windsurf, Cline, and n8n, but the endpoint follows the standard, so other MCP clients work the same way.

Q: How does authentication work?

A: Through your Apify token — the same one you use for any Apify actor. Tool calls are authenticated and billed under your account.

Q: How is it billed?

A: Per tool call, at $0.10 per call, on Apify's pay-per-event model. Idle connections cost nothing.

Q: Can I use it in automated workflows?

A: Yes — via n8n's MCP client node or any programmatic MCP client, you can wire the tools into scheduled briefs, alerts, and enrichment pipelines, not just chat.

Schema stability & versioning

This MCP server follows NexGenData's additive-only contract. New tools and new response fields may be added over time; existing tools and fields are not renamed or removed without a major-version bump and an advance changelog notice. Build agent workflows on the current toolset without worrying about a silent breaking change.

Compliance & legal

• The tools read public market data — prices, positioning reports, rates, and flow data any market participant can access. No authentication to third-party private systems, no anti-bot evasion of paywalled sources.
• The server performs no trading and no movement of funds — it returns data for the model to reason over; trading decisions and actions remain entirely with you.
• Requests route through Apify's compliant infrastructure with polite pacing; authentication is via your own Apify token.
• You are responsible for ensuring downstream use complies with source providers' terms, your jurisdiction's market-data and derivatives regulations, and any licensing rules. Consult counsel before commercial redistribution of the underlying data.

Related NexGenData actors

Part of NexGenData's markets & MCP-bundle cluster — pair this server with:

• Crypto / DeFi MCP — MCP bundle for on-chain and crypto-market data
• Sales Intelligence MCP — MCP bundle for B2B prospecting data
• Supply Chain & Logistics MCP — MCP bundle for trade and logistics data
• Crypto Perp Funding Rates Tracker — Binance perpetual funding rates and mark prices
• US Treasury Auction Results — primary-market Treasury auction data
• Global Central Bank Policy Rates — policy rates across major central banks

Explore the full catalog of 200+ buyer-intent actors and MCP bundles at https://apify.com/nexgendata?fpr=2ayu9b.