Can I see the health score for a specific client?

Yes! Use the `get_client_success_details` tool with the client ID. The agent will return the success score, health status, and other key metrics for that account.

How do I check the active onboarding cycles for my accounts?

Use the `list_client_success_cycles` tool. Your agent will fetch all onboarding and success cycles, allowing you to monitor progress and identify any blocked steps.

Where do I find my ClientSuccess API Key?

Log in to your ClientSuccess account and navigate to **Global Settings > API**. You can generate and copy your personal API key from that section.

ClientSuccess MCP Server for CrewAI 8 tools — connect in under 2 minutes

Name: ClientSuccess
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 8 Tools Framework

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

Connect your ClientSuccess account to any AI agent and take full control of your customer success operations through natural conversation. Streamline how you manage account health and revenue retention natively.

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

Client Oversight — List and retrieve details for all clients, including health scores and status natively
Subscription Intelligence — Access and monitor all subscriptions and contracts associated with specific clients flawlessly
Success Cycle Tracking — Monitor onboarding and success cycles to ensure customer goals are met securely
Interaction Auditing — List and review internal notes and tasks for any specific client flawlessly
Contact Logistics — Access all contacts associated with your clients to maintain relationships securely
integrated Visibility — Retrieve detailed client metadata and profile information directly within your workspace flawlessly

The ClientSuccess MCP Server exposes 8 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 ClientSuccess to CrewAI via MCP

Follow these steps to integrate the ClientSuccess 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 8 tools from ClientSuccess

Why Use CrewAI with the ClientSuccess MCP Server

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

ClientSuccess + CrewAI Use Cases

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

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

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

ClientSuccess MCP Tools for CrewAI (8)

These 8 tools become available when you connect ClientSuccess to CrewAI via MCP:

get_client_success_details

Get detailed information for a specific client

get_my_success_profile

Retrieve information about the authenticated success manager

list_client_subscriptions

List all subscriptions and contracts for a specific client

list_client_success_contacts

List all contacts associated with a specific client

list_client_success_cycles

List all onboarding or success cycles for a client

list_client_success_notes

List all internal notes for a specific client

list_client_success_tasks

List all tasks and to-dos for a specific client

list_success_clients

List all clients in ClientSuccess

Example Prompts for ClientSuccess in CrewAI

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

"List all my clients with a 'Risk' health status."

"Show me the subscriptions for 'Acme Corp'."

"What are the pending tasks for the 'Global Tech' account?"

Troubleshooting ClientSuccess MCP Server with CrewAI

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

ClientSuccess + CrewAI FAQ

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