4,000+ servers built on MCP Fusion
Vinkius
CrewAIFramework
Why use Rappi API MCP Server with CrewAI?

Bring Delivery Services
to CrewAI

Create your Vinkius account to connect Rappi API to CrewAI and start using all 10 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.

MCP Inspector GDPR Free for Subscribers
Get Order DetailGet Order HandoffGet Store AvailabilityGet Store MenuList New OrdersList StoresMark Ready For PickupReject OrderTake OrderUpdate Store Status
ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Rappi API

What is the 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.

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.

How it works

  1. Secure developer approval connecting via the Rappi Developer Hub
  2. Abstract your regional operations extracting your core Client ID alongside its heavy Client Secret
  3. Plug those core variables explicitly below overriding local setups
  4. Trigger commands! Vurb absorbs the intensive REST endpoints securely wrapping responses in natural text formats.

Who is this for?

  • Office Coordinators — schedule and manage multiple large corporate food deliveries across various departments passively tracking arrivals live blindly.
  • Urban Planners — scrap real-world geographic delivery timelines crossing traffic bottlenecks estimating true logistic costs precisely in heavy hubs.
  • LatAm SaaS Integrators — build consolidated order aggregators unifying local Rappi merchant data with alternative distribution networks strictly under one hood.

Built-in capabilities (10)

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

Why CrewAI?

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 Vinkius with zero configuration overhead.

  • 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

See it in action

Rappi API in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Enterprise Security

Why run Rappi API with Vinkius?

The Rappi API connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 10 tools are ready to work instantly without any complex setup.

You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.

Rappi API
Fully ManagedNo server setup
Plug & PlayNo coding needed
SecurePrivacy protected
PrivateYour data is safe
Cost ControlBudget limits
Control1-click disconnect
Auto-UpdatesMaintenance free
High SpeedOptimized for AI
Reliable99.9% uptime
Your credentials and connection tokens are fully encrypted

* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure

01 / Catalog

Over 4,000 integrations ready for AI agents

Explore a vast library of pre-built integrations, optimized and ready to deploy.

02 / Credentials

Connect securely in under 30 seconds

Generate tokens to authenticate and link external services in a single step.

03 / Guardian

Complete visibility into every agent action

Audit live requests, latency, success rates, and active security compliance policies.

04 / FinOps

Optimize spending and track token ROI

Analyze real-time token consumption and cost metrics detailed by connection.

Over 4,000 integrations ready for AI agents
Connect securely in under 30 seconds
Complete visibility into every agent action
Optimize spending and track token ROI

Explore our live AI Agents Analytics dashboard to see it all working

This dashboard is included when you connect Rappi API using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.

Why Vinkius

Rappi API and 4,000+ other AI tools. No hosting, no code, ready to use.

Professionals who connect Rappi API to CrewAI through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.

4,000+MCP Integrations
<40msResponse time
100%Fully managed
Raw MCP
Vinkius
Ready-to-use MCPsFind and configure each manually4,000+ MCPs ready to use
Connection SetupManual coding & server setup1-click instant connection
Server HostingYou host it yourself (needs 24/7 uptime)100% hosted & managed by Vinkius
Security & PrivacyStored in plaintext config filesBank-grade encrypted vault
Activity VisibilityBlind execution (no logs or tracking)Live dashboard with real-time logs
Cost ControlRunaway AI token spend riskAutomatic budget limits
Revoking AccessMust delete files or code to stop1-click disconnect button
The Vinkius Advantage

How Vinkius secures Rappi API for CrewAI

Every request between CrewAI and Rappi API is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

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.

05

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.

06

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.

07

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.

08

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.

09

MCP tools not discovered

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

10

Agent not using tools

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

11

Timeout errors

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

12

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.

Explore More MCP Servers

View all →