2,500+ MCP servers ready to use
Vinkius

Moova MCP Server for CrewAI 14 tools — connect in under 2 minutes

Built by Vinkius GDPR 14 Tools Framework

Connect your CrewAI agents to Moova through Vinkius, pass the Edge URL in the `mcps` parameter and every Moova 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="Moova Specialist",
    goal="Help users interact with Moova effectively",
    backstory=(
        "You are an expert at leveraging Moova 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 Moova "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 14 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Moova
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 Moova MCP Server

Connect your Moova B2B logistics account to any AI agent and orchestrate your entire delivery operation through natural conversation.

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

  • Shipment Management — Create, update, and cancel delivery orders with full origin/destination address details and contact information
  • Real-time Tracking — Follow every shipment through GPS-powered tracking events including carrier handoffs, delivery attempts, and proof of delivery
  • Smart Quoting — Get instant shipping cost estimates between any two addresses using Moova's intelligent carrier routing engine
  • Label Generation — Download printable shipping labels with barcodes and QR codes for any registered shipment
  • Coverage Intelligence — Query available delivery zones across Argentina and Latin America before committing to an order
  • Webhook Automation — Configure real-time notifications for shipment status changes to keep your systems synchronized

The Moova MCP Server exposes 14 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 Moova to CrewAI via MCP

Follow these steps to integrate the Moova 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 14 tools from Moova

Why Use CrewAI with the Moova MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Moova 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

Moova + CrewAI Use Cases

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

01

Automated multi-step research: a reconnaissance agent queries Moova 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 Moova, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain Moova 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 Moova against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Moova MCP Tools for CrewAI (14)

These 14 tools become available when you connect Moova to CrewAI via MCP:

01

cancel_shipment

Once cancelled, the shipment cannot be reactivated and a new one must be created if needed. Cancel an active shipment order

02

create_shipment

Requires origin and destination addresses with full street details, contact information, and package dimensions. Moova will automatically assign the optimal carrier and route based on real-time availability. Create a new logistics shipment

03

create_webhook

Essential for keeping your e-commerce platform synchronized with delivery progress. Register a new webhook for shipment events

04

delete_webhook

Remove a webhook endpoint

05

get_account_info

Get merchant account information

06

get_budget

Returns pricing from available carriers including express, same-day, and standard delivery options. Get a shipping cost estimate

07

get_shipment

Get full details of a specific shipment

08

get_shipment_label

The label includes barcode, QR code, and all routing information required by the assigned carrier. Download the shipping label for a shipment

09

get_shipment_status

Get the current status of a shipment

10

list_coverage_zones

List all available delivery coverage zones

11

list_shipments

Can be filtered by shipment status (e.g., CREATED, IN_TRANSIT, DELIVERED, CANCELLED) to narrow results. List all shipments with optional status filter

12

list_webhooks

List all registered webhooks

13

track_shipment

Get real-time tracking events for a shipment

14

update_shipment

Changes are not allowed after the carrier has collected the package. Update shipment details before pickup

Example Prompts for Moova in CrewAI

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

01

"Create a delivery from 'Av. Corrientes 1234, Buenos Aires' to 'Av. Santa Fe 5678, Buenos Aires' for Juan Pérez."

02

"How much would it cost to ship from Palermo to Belgrano in Buenos Aires?"

03

"Track my shipment MOV-28491-AR and tell me where it is right now."

Troubleshooting Moova MCP Server with CrewAI

Common issues when connecting Moova 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.

Moova + CrewAI FAQ

Common questions about integrating Moova 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 Moova to CrewAI

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