How to Use the ClientSuccess MCP in CrewAI

Q: How do I connect ClientSuccess to CrewAI?

Pass your Vinkius endpoint directly into the mcps parameter when defining your agent. The framework automatically maps the exposed endpoints into actionable tools.

Q: How do I restrict ClientSuccess access in CrewAI?

Import MCPServerHTTP from crewai.mcp and define a toolfilter. This explicitly denies access to sensitive endpoints like internal notes.

Deploy autonomous account management crews by connecting the ClientSuccess MCP Server to CrewAI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect ClientSuccess MCP to CrewAI

Create your Vinkius account to connect ClientSuccess to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup ClientSuccess with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Coordinate CrewAI Account Teams

Providing `list_client_success_contacts` feeds raw stakeholder data to your researcher agent. That worker compiles a dossier and passes it to the strategy agent in shared memory. Setting up this pipeline requires almost zero code. You drop the Vinkius URL into the `mcps` array, and the entire squad gains access to the CRM data instantly.

Monitor Subscription Health

Financial analyst agents use `list_client_subscriptions` to gain visibility into upcoming renewals. A separate moderator agent reviews this output and drafts a personalized email for the account owner. Filtering operations keeps specialized workers focused. You configure your MCP setup with `tool_filter` so the analyst only sees billing endpoints and ignores implementation tasks.

Synthesize Internal Notes

Digging into `list_client_success_notes` provides the raw history of customer interactions. The summarizer agent reads these logs to brief the success manager before their quarterly business review. These autonomous operations run without human intervention. The system executes sequentially, ensuring the researcher finishes pulling the records before the writer drafts the summary.

Setup guide

Set up ClientSuccess MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke ClientSuccess tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="ClientSuccess Analyst",
    goal="Access and analyze ClientSuccess data via MCP.",
    backstory="Expert analyst with direct ClientSuccess access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent ClientSuccess transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="ClientSuccess Analyst",
        goal="Access and analyze ClientSuccess data via MCP.",
        backstory="Expert analyst with direct ClientSuccess access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent ClientSuccess transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by ClientSuccess. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect ClientSuccess now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about ClientSuccess MCP in CrewAI

Pass your Vinkius endpoint directly into the `mcps` parameter when defining your agent. The framework automatically maps the exposed endpoints into actionable tools.

Your specialized workers share memory but execute their specific tasks independently. One agent can fetch subscriptions while another lists pending tasks.

Import `MCPServerHTTP` from `crewai.mcp` and define a `tool_filter`. This explicitly denies access to sensitive endpoints like internal notes.

The framework supports stdio, SSE, and Streamable HTTP out of the box. Vinkius endpoints default to HTTP for maximum reliability across distributed teams.

We execute all requests for your subscription details and task lists inside a secure V8 Isolate Sandbox. The ephemeral environment destroys the connection data the moment the crew finishes its run.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript