2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 14 Tools Framework

Connect your CrewAI agents to Cornershop through Vinkius, pass the Edge URL in the `mcps` parameter and every Cornershop 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="Cornershop Specialist",
    goal="Help users interact with Cornershop effectively",
    backstory=(
        "You are an expert at leveraging Cornershop 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 Cornershop "
        "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)
Cornershop
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 Cornershop MCP Server

Connect your Cornershop by Uber B2B account to any AI agent and manage your last-mile grocery delivery operations through natural conversation.

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

  • Store & Product Discovery — Search through connected retail partners (Jumbo, Lider, pharmacies), browse their aisles, and find specific SKUs with real-time pricing and availability
  • Order Creation — Construct shopping carts dynamically and place delivery orders directly through your AI agent
  • Live Tracking — Monitor the real-time status of your orders, from picking to delivery, including GPS tracking of the assigned Shopper
  • Order Modification — Add or remove items from the cart while the Shopper is still in the store, without opening the mobile app
  • Shopper Communication — Retrieve contact details for assigned Shoppers to resolve delivery issues instantly

The Cornershop 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 Cornershop to CrewAI via MCP

Follow these steps to integrate the Cornershop 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 Cornershop

Why Use CrewAI with the Cornershop MCP Server

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

Cornershop + CrewAI Use Cases

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

01

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

03

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

Cornershop MCP Tools for CrewAI (14)

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

01

cancel_order

Note: Orders can only be cancelled without penalty if the shopper hasn't started picking. Cancel a pending order

02

create_order

Requires a JSON string defining the cart (product IDs, quantities) and delivery address details. Place a new delivery order

03

create_webhook

g., shopper_assigned, order_delivered). Create a new explicit webhook

04

get_order

Get full details of a specific order

05

get_product

Get details of a specific product

06

get_store

Get details of a specific store branch

07

list_orders

List your delivery orders

08

list_shoppers

Get information about the assigned Shopper

09

list_store_aisles

List categories and aisles of a store

10

list_stores

g. Jumbo, Lider, pharmacies). Can be geographically filtered by latitude and longitude. List available grocery stores and partners

11

list_webhooks

List configured order webhooks

12

search_products

Returns matching SKUs, names, current pricing, and availability. Search for specific groceries and products

13

track_order

Get real-time tracking for a delivery

14

update_order

Useful for last-minute replacements or additions. Update an active order (e.g. add/remove items)

Example Prompts for Cornershop in CrewAI

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

01

"Search for Jumbo stores near latitude -33.4372 and longitude -70.6506 (Santiago Centro)."

02

"Where is the shopper for my order #CS-44919?"

03

"Place an order at Lider (ID: LDR-10) for 2 units of SKU 'Milk-Whole-1L' and deliver into the corporate office."

Troubleshooting Cornershop MCP Server with CrewAI

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

Cornershop + CrewAI FAQ

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

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