Does order placement via the API bypass the normal Rappi checkout security rules?

No. The `place_order` tool uses your pre-authenticated method securely. Bank validations, anti-fraud algorithms, and location checks apply exactly as they would natively in the application avoiding compliance breaches entirely.

Can I explicitly track multiple concurrent active orders dynamically simultaneously?

Yes! Your agent can iterate over an array of active Order IDs using the `get_order_status` tool consistently. It parses coordinate updates and ETA drops, outputting a consolidated table summing up your entire inbound fleet seamlessly.

Are the store identifiers (storeId) universally stable across regions?

Store IDs are fundamentally unique keys generated explicitly by Rappi's catalog backend. They remain static for the lifetime of that specific branch location. Searching via `list_nearby_stores` initially is recommended to cache the correct target IDs dynamically.

Rappi API MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Rappi API
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Rappi API through the Vinkius — pass the Edge URL in the `mcps` parameter and every Rappi 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="Rappi API Specialist",
    goal="Help users interact with Rappi API effectively",
    backstory=(
        "You are an expert at leveraging Rappi 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 Rappi API "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 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 Rappi API MCP Server

Empower your intelligent agents directly with Rappi API, the dominant delivery and logistics super-app bridging Latin America. Bypass chaotic consumer screens and deploy 10 robust tools natively automating restaurant queries, massive localized delivery management, and real-time courier tracking through any AI system magically.

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

What you can do

Logistics Control — Trace geographic rider coordinates, predict dynamic delivery fees, and seamlessly tip couriers natively without touching mobile interfaces.
Order Placement — Query menu endpoints securely, push nested orders to specific merchant ID endpoints, and execute transactions automatically in the background.
Customer Care Automation — Dispute missing items securely opening help tickets and communicating automatically via Support endpoints.
Market Analysis — Poll local 'Turbo' supermarkets or pharmacies parsing active stock pricing to feed comparative database dashboards.

The Rappi API MCP Server exposes 10 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 Rappi API to CrewAI via MCP

Follow these steps to integrate the Rappi 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 10 tools from Rappi API

Why Use CrewAI with the Rappi API MCP Server

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

Rappi API + CrewAI Use Cases

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

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

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

Rappi API MCP Tools for CrewAI (10)

These 10 tools become available when you connect Rappi API to CrewAI via MCP:

get_order_detail

Get full details for a specific order

get_order_handoff

Get handoff confirmation codes for an order

get_store_availability

Check availability status of a store

get_store_menu

Retrieve the full menu of a store

list_new_orders

List new incoming orders awaiting acceptance

list_stores

List all registered stores under your account

mark_ready_for_pickup

Signal that an order is ready for courier pickup

reject_order

Reject an incoming order with a reason

take_order

Accept and start preparing an incoming order

update_store_status

Open or close a store for receiving orders

Example Prompts for Rappi API in CrewAI

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

"List nearby stores in the 'pharmacy' category around coordinates 4.6097, -74.0817."

"Check the delivery state and ETA for my active order number 8812920."

"Cancel the active order 88910 immediately citing missing items from the receipt."

Troubleshooting Rappi API MCP Server with CrewAI

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

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

Rappi API + CrewAI FAQ

Common questions about integrating Rappi 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.