How to Use the Enverus Energy Intelligence MCP in LlamaIndex

Q: How do I load the Enverus Energy Intelligence MCP Server tools into LlamaIndex?

Install llama-index-tools-mcp. Initialize a BasicMCPClient, wrap it in an McpToolSpec, and call totoollistasync() before passing the array to your FunctionAgent.

Q: Can LlamaIndex embed the output from Enverus Energy Intelligence well searches?

Yes. When your agent calls listoilandgaswells, it can take the returned JSON arrays and index them as document nodes. This makes specific well coordinates searchable.

Q: Does LlamaIndex support filtering which MCP tools the agent can use?

Yes. You can restrict the agent using the allowedtools parameter. If you only want it querying permits, you expose listdrillingpermits and hide the rest.

Index live drilling data and well telemetry directly into your LlamaIndex RAG applications using this MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Enverus Energy Intelligence MCP to LlamaIndex

Create your Vinkius account to connect Enverus Energy Intelligence to LlamaIndex and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Enverus Energy Intelligence with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Index Energy Market Summaries

The `get_energy_market_intelligence_summary` tool pulls high-level market trends directly into your LlamaIndex vector store. Your agent doesn't just read the briefing once. It embeds the text so you can run semantic queries against months of market shifts. You follow up by indexing the output of `list_energy_m_and_a_deals`. When you ask your agent about consolidation in the Permian, it retrieves actual transaction records instead of hallucinating corporate mergers.

Ground RAG Apps with LlamaIndex and MCP

The `get_rig_technical_details` tool fetches the exact mechanical settings and current activity for specific rigs. You pipe this raw mechanical data into your knowledge base to anchor your search results in reality. Combine it with `list_active_drilling_rigs` to maintain a living index of regional hardware deployment. Your agent cross-references user queries against hard telemetry, ensuring every answer traces back to a verified rig.

Vectorize Basin Activity Metrics

The `list_basin_specific_activity` tool isolates rigs and wells by geological boundaries. Your LlamaIndex application embeds these regional constraints, allowing you to ask natural language questions about specific shale plays. Look, here's the deal. You add `quick_energy_asset_audit` to your MCP tool spec to keep the well counts fresh. The agent retrieves the current tally, compares it to your indexed historical data, and generates a grounded report on basin depletion.

Setup guide

Set up Enverus Energy Intelligence MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all Enverus Energy Intelligence MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to Enverus Energy Intelligence tools.",
)
response = await agent.run("List recent Enverus Energy Intelligence data")

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Enverus Energy Intelligence. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Enverus Energy Intelligence now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Enverus Energy Intelligence MCP in LlamaIndex

Install `llama-index-tools-mcp`. Initialize a `BasicMCPClient`, wrap it in an `McpToolSpec`, and call `to_tool_list_async()` before passing the array to your FunctionAgent.

Yes. When your agent calls `list_oil_and_gas_wells`, it can take the returned JSON arrays and index them as document nodes. This makes specific well coordinates searchable.

CSVs go stale the minute you export them. By giving your agent access to `get_enverus_api_metadata` and live endpoints, your knowledge base updates itself dynamically.

Yes. You can restrict the agent using the `allowed_tools` parameter. If you only want it querying permits, you expose `list_drilling_permits` and hide the rest.

Vinkius handles the connection via a sandboxed environment. Your agent pulls data from `list_basin_specific_activity` using a single endpoint token. The infrastructure drops the container immediately after the request finishes, leaving no trace of your geological coordinates.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript