Where do I find my Kustomer API Key?

Log in to Kustomer, navigate to **Settings** > **Security** > **API Keys**, and create a new key with the necessary scopes.

Can I see chat messages in real-time?

The `list_conversation_messages` tool fetches the current history. While not a streaming 'live' view, it provides the most recent state.

Does this support creating customers?

The current version focus on data retrieval and analysis. Creation tools are planned for future updates.

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

Name: Kustomer
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

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

Connect your AI agent to Kustomer to streamline your support operations and customer data auditing.

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

Key Features

Omnichannel Conversation Access — List and audit support conversations from email, chat, and social channels
Customer 360 View — Fetch detailed customer profiles including custom attributes and history
Message Auditing — Retrieve the full message history for any support interaction
Timeline Search — Perform deep searches across customer timelines using complex JSON filters
Service Context — List support queues, agents, and custom data classes (Klasses)

Simple Setup

1. Subscribe to this server
2. Log in to Kustomer and generate a Bearer API Key (Settings > Security > API Keys)
3. Enter your key in the configuration panel
4. Start managing your support data via natural language

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

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

Why Use CrewAI with the Kustomer MCP Server

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

Kustomer + CrewAI Use Cases

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

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

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

Kustomer MCP Tools for CrewAI (10)

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

check_kustomer_api_status

Check the status of the Kustomer API

get_conversation_details

Get details for a specific conversation

get_customer_profile

Get details for a specific customer

list_conversation_messages

List all messages in a conversation

list_data_klasses

List Kustomer custom data classes (Klasses)

list_kustomer_agents

List all support agents (users)

list_kustomer_customers

Essential for identifying customer IDs for support auditing. List all customers in Kustomer

list_support_conversations

List recent support conversations

list_support_queues

g., Billing, Technical Support) defined in Kustomer. List active support queues

search_kustomer_timeline

Provide filters as a JSON string. Perform a deep search across the customer timeline

Example Prompts for Kustomer in CrewAI

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

"List the 10 most recent support conversations in Kustomer"

"Show the full profile for customer '65a4b3c2d1e0f'"

"Search the timeline for customers from 'Brazil'"

Troubleshooting Kustomer MCP Server with CrewAI

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

Kustomer + CrewAI FAQ

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