2,500+ MCP servers ready to use
Vinkius

Taranis MCP Server for CrewAI 12 tools — connect in under 2 minutes

Built by Vinkius GDPR 12 Tools Framework

Connect your CrewAI agents to Taranis through Vinkius, pass the Edge URL in the `mcps` parameter and every Taranis tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Vinkius supports streamable HTTP and SSE.

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Taranis Specialist",
    goal="Help users interact with Taranis effectively",
    backstory=(
        "You are an expert at leveraging Taranis tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Taranis "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 12 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Taranis
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Taranis MCP Server

Connect your Taranis AI Scouting API to any AI agent and take full control of AI-powered crop threat detection, ultra-high-resolution imagery analysis, field scouting recommendations, and precision agriculture decision-making through natural conversation.

When paired with CrewAI, Taranis becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Taranis tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

  • Organizations — List all agricultural organizations and farms in your Taranis account
  • Field Management — View all monitored fields with crop types, boundaries, and growth stages
  • Flight History — Review all drone and aircraft flight missions with imagery acquisition dates
  • Flight Imagery — Access ultra-high-resolution orthomosaics, DSMs, and NDVI maps from each flight
  • All Detections — Get comprehensive AI-detected threats (weeds, diseases, pests, nutrients) in any field
  • Threat Summary — View consolidated threat severity assessments and trend analysis per field
  • Scouting Recommendations — Receive AI-powered action plans for targeted field scouting missions
  • Multispectral Analysis — Access NDVI, NDRE, and GNDVI vegetation indices for vigor assessment
  • Weed Detection — Identify specific weed species with coverage estimates and herbicide recommendations
  • Disease Detection — Detect crop diseases with severity levels and fungicide treatment suggestions
  • Nutrient Analysis — Identify nutrient deficiencies with variable rate fertilization recommendations

The Taranis MCP Server exposes 12 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Taranis to CrewAI via MCP

Follow these steps to integrate the Taranis MCP Server with CrewAI.

01

Install CrewAI

Run pip install crewai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

03

Customize the agent

Adjust the role, goal, and backstory to fit your use case

04

Run the crew

Run python crew.py. CrewAI auto-discovers 12 tools from Taranis

Why Use CrewAI with the Taranis MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Taranis through the Model Context Protocol.

01

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

02

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

03

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

04

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Taranis + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Taranis MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries Taranis for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries Taranis, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain Taranis tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries Taranis against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Taranis MCP Tools for CrewAI (12)

These 12 tools become available when you connect Taranis to CrewAI via MCP:

01

get_detections

Returns detection locations (GPS coordinates), threat types (weeds, diseases, pests, nutrient deficiencies), severity levels, confidence scores, affected area estimates, and recommended actions. Detections are classified by AI models trained on millions of field images for sub-millimeter accuracy. Essential for early threat identification, targeted scouting, and precision treatment planning. AI agents should use this when users ask "show me all detections in my field", "what threats were detected in field X", or need comprehensive threat analysis before planning field operations. Optional threatType filters detections by specific threat category. Get all AI-detected crop threats (weeds, diseases, pests, nutrient deficiencies) in a field

02

get_disease_detections

Returns disease locations, pathogen identification where possible, severity levels (early, moderate, advanced), affected plant parts, and recommended fungicide treatments. Essential for early disease intervention, fungicide planning, and yield loss prevention. AI agents should reference this when users ask "what diseases are in my soybean field", "show disease progression over time", or need disease-specific analysis for crop protection decisions. Get crop disease detections and severity assessments for a field

03

get_field_details

Essential for understanding field context before analyzing detections, planning scouting missions, or generating management recommendations. AI agents should reference this when users ask "tell me about this field", "what crop is planted in field X", or need detailed field metadata for context-aware analysis. Get detailed information about a specific agricultural field

04

get_fields

Returns field names, IDs, boundaries (GeoJSON polygons), area in hectares/acres, crop type, planting dates, and monitoring status. Essential for farm management overview, field inventory, and selecting target fields for threat detection and scouting analysis. AI agents should use this when users ask "show me all fields in my organization", "list monitored fields", or need to identify available fields for detection or flight queries. Optional orgId filters fields by specific organization. List all agricultural fields monitored by Taranis for an organization

05

get_flight_imagery

Returns orthomosaic mosaics, digital surface models (DSM), digital terrain models (DTM), normalized difference vegetation index (NDVI) maps, and true-color RGB composites. Essential for visual crop assessment, change detection between flights, and downloading high-resolution imagery for GIS analysis. AI agents should reference this when users ask "show me the latest imagery from this flight", "get the NDVI map for flight X", or need specific imagery products for field analysis. Get ultra-high-resolution imagery products from a specific flight mission

06

get_flights

Returns flight dates, times, aircraft type, imagery resolution, weather conditions during flight, coverage percentage, and processing status. Essential for understanding imagery acquisition history, assessing data quality, and selecting specific flights for detailed analysis. AI agents should use this when users ask "show me all flights over my corn field", "what imagery was captured last week", or need flight metadata before accessing specific imagery products. List all drone or aircraft flights that captured imagery for a specific field

07

get_multispectral_imagery

Supports indices including NDVI (Normalized Difference Vegetation Index), NDRE (Normalized Difference Red Edge), GNDVI (Green NDVI), and custom band combinations. Returns imagery layers, statistical summaries (mean, min, max, std), and zone classifications. Essential for crop vigor assessment, variable rate application planning, and growth stage monitoring. AI agents should reference this when users ask "show me NDVI map for my field", "get multispectral analysis", or need vegetation index data for precision agriculture planning. Get multispectral imagery and vegetation indices (NDVI, NDRE, GNDVI) for a field

08

get_nutrient_detections

Returns deficiency locations, severity estimates, affected growth stages, and variable rate fertilization recommendations. Essential for precision nutrient management, yield optimization, and cost-efficient fertilization planning. AI agents should use this when users ask "does my field have nutrient deficiencies", "where do I need to apply nitrogen", or need nutrient-specific analysis for variable rate application planning. Get nutrient deficiency detections and fertilization recommendations for a field

09

get_organizations

Returns organization names, IDs, contact information, and field counts. Essential for multi-account management, selecting target organizations for field analysis, and understanding the scope of monitored agricultural operations. AI agents should use this when users ask "show me all my organizations", "list farms I have access to", or need to identify available organizations before querying fields or detections. List all organizations available to the user in Taranis platform

10

get_scouting_recommendations

Returns specific action items including ground truth verification locations, recommended scouting patterns, treatment suggestions, timing recommendations, and priority levels. Essential for field team coordination, targeted scouting missions, and data-driven treatment decisions. AI agents should use this when users ask "what should I scout for in my field this week", "give me scouting recommendations", or need AI-generated action plans based on latest imagery analysis. Get AI-powered scouting recommendations and action plans for a field

11

get_threats

Returns threat categories, overall severity ratings (low, medium, high, critical), affected area percentages, trend analysis (increasing, stable, decreasing), and priority rankings. Essential for quick field health assessment, prioritizing scouting missions, and making informed treatment decisions. AI agents should reference this when users ask "what is the overall threat level in my field", "summarize field health status", or need a high-level threat overview before diving into individual detections. Get consolidated threat summary and severity assessment for a field

12

get_weed_detections

Returns weed locations, estimated coverage area, species classification, growth stage, and herbicide resistance indicators. Essential for targeted spot spraying, herbicide selection, and resistance management. AI agents should use this when users ask "where are the weeds in my field", "what weed species were detected", or need weed-specific analysis for precision herbicide application. Get specific weed species detections and infestation maps for a field

Example Prompts for Taranis in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Taranis immediately.

01

"Show me all AI-detected threats in my corn field from the latest flight."

02

"Generate scouting recommendations for my soybean field this week."

03

"What is the overall threat level and NDVI trend for my wheat field this season?"

Troubleshooting Taranis MCP Server with CrewAI

Common issues when connecting Taranis to CrewAI through the Vinkius, and how to resolve them.

01

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
02

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
03

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
04

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Taranis + CrewAI FAQ

Common questions about integrating Taranis MCP Server with CrewAI.

01

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
02

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
03

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
04

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
05

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

Connect Taranis to CrewAI

Get your token, paste the configuration, and start using 12 tools in under 2 minutes. No API key management needed.