How to Use the Enverus Energy Intelligence MCP in CrewAI

Q: How can I use CrewAI and Enverus Energy Intelligence to monitor a specific oil basin?

You'd create a crew. An 'Observer' agent periodically runs listbasinspecificactivity. If it detects changes, it tasks an 'Investigator' agent to pull details with getwellproductiontelemetry for the new assets.

Q: Can different agents in my CrewAI crew use different Enverus Energy Intelligence tools?

Yes. CrewAI's MCPServerHTTP class lets you use a toolfilter when defining the connection. This means you can create a 'Research' agent that can only use list tools and an 'Analysis' agent that can only use get tools.

Q: How do I check if my setup is working?

Have one of your agents call the getenverusapimetadata tool. It confirms the connection to the MCP server is live and that your authentication with the underlying Enverus API is successful.

Q: Is my crew's analysis of proprietary drilling permits safe with Enverus Energy Intelligence and CrewAI?

Yes. All communication, including data from listdrillingpermits, is encrypted in transit. Vinkius processes each tool call in a separate, sandboxed V8 isolate that is destroyed after the call completes, ensuring your crew's work isn't exposed.

Deploy autonomous crews on Enverus data with CrewAI. Assign agents to research basins, analyze production, and report on market activity.

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 CrewAI

Create your Vinkius account to connect Enverus Energy Intelligence to CrewAI 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 CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Assemble an Analyst Crew

Assign a 'Scout' agent to use `list_active_drilling_rigs` and `list_drilling_permits` to find new activity. A second 'Analyst' agent can then take that output and dig deeper, using `get_rig_technical_details` and `get_well_production_telemetry` for each discovery. The agents share context, so the Scout's findings become the Analyst's work queue automatically. A final 'Reporter' agent can take the detailed analysis and use `get_energy_market_intelligence_summary` to frame it with market context for a briefing.

Autonomous M&A Scouting

Build a crew dedicated to finding acquisition targets. One agent runs `list_energy_m_and_a_deals` to watch for transactions. When it finds one, it passes the company names to another agent that uses `list_oil_and_gas_wells` to audit their holdings. This creates a powerful, autonomous pipeline. You don't just get a list of deals; you get a preliminary analysis of the assets involved. The crew works together, turning raw data into actionable intelligence without you lifting a finger.

Your CrewAI MCP Server Integration

Connecting your crew is simple. Just add the Vinkius MCP Server URL to your Agent's `mcps` list. For more control, you can use `MCPServerHTTP` to give different agents access to different tools—your Scout might only need `list_` tools, while your Analyst gets the `get_` tools. This MCP Server architecture is perfect for CrewAI's role-based model. You can build highly specialized agents that only have the permissions they need to do their specific job, which is a cleaner and more secure way to build.

Setup guide

Set up Enverus Energy Intelligence MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Enverus Energy Intelligence tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Enverus Energy Intelligence Analyst",
    goal="Access and analyze Enverus Energy Intelligence data via MCP.",
    backstory="Expert analyst with direct Enverus Energy Intelligence access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Enverus Energy Intelligence transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Enverus Energy Intelligence Analyst",
        goal="Access and analyze Enverus Energy Intelligence data via MCP.",
        backstory="Expert analyst with direct Enverus Energy Intelligence access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Enverus Energy Intelligence transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

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 CrewAI

You'd create a crew. An 'Observer' agent periodically runs `list_basin_specific_activity`. If it detects changes, it tasks an 'Investigator' agent to pull details with `get_well_production_telemetry` for the new assets.

Yes. CrewAI's `MCPServerHTTP` class lets you use a `tool_filter` when defining the connection. This means you can create a 'Research' agent that can only use `list_` tools and an 'Analysis' agent that can only use `get_` tools.

Not at all. The easiest way is to pass the Vinkius URL directly into the `mcps` parameter when you define your Agent. CrewAI handles the rest, making the Enverus tools available to your crew.

Have one of your agents call the `get_enverus_api_metadata` tool. It confirms the connection to the MCP server is live and that your authentication with the underlying Enverus API is successful.

Yes. All communication, including data from `list_drilling_permits`, is encrypted in transit. Vinkius processes each tool call in a separate, sandboxed V8 isolate that is destroyed after the call completes, ensuring your crew's work isn't exposed.

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