How do I find my Perenual API Key?

Register for a free or paid account at [**perenual.com/docs/api**](https://perenual.com/docs/api), and you will find your API Key in your dashboard. Copy and paste it below.

Does it support disease identification?

Yes. The `search_plant_diseases` tool allows your agent to audit common pests and diseases and retrieve recommended solutions.

Are care guides included for all species?

Yes. The `get_plant_care_guide` tool retrieves specific maintenance instructions including watering frequency and sunlight exposure for most species.

Perenual Plant API MCP Server for CrewAI 5 tools — connect in under 2 minutes

Name: Perenual Plant API
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 5 Tools Framework

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

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Perenual Plant API Specialist",
    goal="Help users interact with Perenual Plant API effectively",
    backstory=(
        "You are an expert at leveraging Perenual Plant API 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 Perenual Plant API "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 5 available tools "
        "and what they can do."
    ),
)

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

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 Perenual Plant API MCP Server

Empower your AI agent to orchestrate your entire botanical research and plant auditing workflow with the Perenual Plant API, the comprehensive source for species-specific care data. By connecting Perenual to your agent, you transform complex plant searches into a natural conversation. Your agent can instantly identify plant species, audit watering and sunlight requirements, and query disease identification metadata without you ever touching a gardening portal. Whether you are conducting horticultural research or managing local greenhouse constraints, your agent acts as a real-time botanical consultant, ensuring your data is always verified and localized.

When paired with CrewAI, Perenual Plant API becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Perenual Plant API 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

Species Auditing — Search for thousands of plant species by common or scientific name and retrieve detailed metadata, including IDs and names.
Care Oversight — Audit specific care guides for any species to understand watering, sunlight, and maintenance distribution instantly.
Disease Discovery — Search for common plant pests and diseases to identify relevant biological markers for your greenhouse.
Horticultural Intelligence — Retrieve high-resolution details for specific species IDs to assist in deep-dive botanical classification.
Operational Monitoring — Check API status to ensure your botanical research workflow is always operational.

The Perenual Plant API MCP Server exposes 5 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 Perenual Plant API to CrewAI via MCP

Follow these steps to integrate the Perenual Plant API MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

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

Customize the agent

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

Run the crew

Run python crew.py. CrewAI auto-discovers 5 tools from Perenual Plant API

Why Use CrewAI with the Perenual Plant API MCP Server

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

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

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

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

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

Perenual Plant API + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Perenual Plant API MCP Server delivers measurable value.

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

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

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

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

Perenual Plant API MCP Tools for CrewAI (5)

These 5 tools become available when you connect Perenual Plant API to CrewAI via MCP:

check_api_status

Check if the Perenual service is operational

get_plant_care_guide

Get care instructions and guides for a specific plant

get_plant_details

Get full details for a specific plant by species ID

search_plant_diseases

Search for common plant pests and diseases

search_plants

Search for plants by common or scientific name

Example Prompts for Perenual Plant API in CrewAI

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

"Search for 'monstera' using Perenual Plant API."

"What is the care guide for species ID 5257?"

"Search for plant diseases related to 'root rot'."

Troubleshooting Perenual Plant API MCP Server with CrewAI

Common issues when connecting Perenual Plant API to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

Perenual Plant API + CrewAI FAQ

Common questions about integrating Perenual Plant API MCP Server with CrewAI.

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.

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.

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.

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.

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.