Can my agent check why a specific rep is not getting leads?

Yes. Ask your agent to get queue details for your distribution group. It surfaces the weights and distribution history for each member, allowing you to quickly spot misconfigured weights or availability issues that block lead routing.

How do I generate a booking link for a prospect during a chat?

Provide your agent with the prospect's email and name, and specify a Concierge route. The agent calls the Chili Piper API to generate a personalized, ephemeral booking link that you can share immediately in your outreach.

Can I audit all meetings that ended as a 'No-Show' this week?

Absolutely. List your meetings for the desired date range and ask your agent to filter for No-Show status. It aggregates the data directly from Chili Piper, helping you track pipeline health without manual exports.

Chili Piper MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Chili Piper
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

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

Connect your Chili Piper account to any AI agent and turn inbound leads into meetings through natural conversation.

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

Concierge Routes — List and audit your inbound routing rules that dictate how leads connect with your team
Distribution Queues — Manage SDR and AE groups, check weights, and monitor round-robin distributions
Instant Booking — Generate ephemeral booking links for specific leads and routes directly in your chat
Meeting Management — List scheduled meetings, check status (Booked, No-Show), and handle cancellations with reasons
Team Availability — Check any member's free slots and availability windows across Google or Outlook calendars

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

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

Why Use CrewAI with the Chili Piper MCP Server

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

Chili Piper + CrewAI Use Cases

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

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

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

Chili Piper MCP Tools for CrewAI (10)

These 10 tools become available when you connect Chili Piper to CrewAI via MCP:

cancel_meeting

Irreversibly vaporize explicit validations extracting active scheduling blocks

generate_booking_link

Provision a highly-available JSON Payload generating hard Calendar links

get_availability

Retrieve explicit analytics/statistics representing physical white-space

get_meeting_details

Retrieve the exact structural matching verifying explicit Meeting payloads

get_queue_details

Get an explicit full Chili Piper Queue layout including weight distributions

get_route_details

Perform structural extraction of properties driving active Router mapping

list_meetings

Enumerate explicitly attached structured rules exporting active scheduling lists

list_members

Retrieve explicit Cloud logging tracing explicit Member accounts

list_queues

Identify precise active arrays spanning native Round-Robin grouping

list_routes

Identify bounded logical arrays managing top-level unified Concierge rules in Chili Piper

Example Prompts for Chili Piper in CrewAI

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

"List all Concierge routes"

"Generate a booking link for sarah@example.com using the 'Inbound Demo' route"

"What is the availability of rep @JohnDoe for tomorrow?"

Troubleshooting Chili Piper MCP Server with CrewAI

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

Chili Piper + CrewAI FAQ

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