How to Use the Chaindesk MCP in CrewAI

Q: How do I configure the Chaindesk MCP Server in CrewAI?

Install the dependencies with pip install crewaitools. You can pass the Vinkius URL directly into the mcps array on your Agent definition for immediate access.

Q: Can CrewAI restrict which Chaindesk tools an agent sees?

Yes. Import MCPServerHTTP from crewai.mcp and use toolfilter. This prevents your researcher agent from accidentally calling deleteagent.

Deploy a CrewAI team that manages Chaindesk knowledge bases, audits chat logs, and handles autonomous customer support escalations.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Chaindesk MCP to CrewAI

Create your Vinkius account to connect Chaindesk 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 Chaindesk with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Segment support tasks across agents

One bot cannot handle complex technical support alone. Connecting this MCP Server means you assign a researcher agent to scan documentation via `get_datastore` while a responder agent drafts the reply. The crew collaborates in shared memory. Once the researcher finds the fix, the responder formats the output and uses `query_agent` to push the final resolution to the user.

Audit chat logs with CrewAI MCP Server

Quality assurance usually requires managers reading endless transcripts. A dedicated monitor agent can run `list_conversations` every night to pull the day's activity. It then loops through `get_messages` to analyze sentiment and identify unresolved tickets. The agent compiles a report of failing interactions and flags them for human review the next morning.

Keep knowledge bases fresh automatically

Outdated FAQs cause support bottlenecks. You can instruct an editor agent to watch your product changelog and trigger `upsert_datasource` whenever a new feature ships. The system immediately updates the underlying index. A secondary agent can then run `update_agent` to adjust the system prompt, ensuring the bot knows exactly how to talk about the new release.

Setup guide

Set up Chaindesk 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 Chaindesk tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent Chaindesk 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="Chaindesk Analyst",
        goal="Access and analyze Chaindesk data via MCP.",
        backstory="Expert analyst with direct Chaindesk access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Chaindesk 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 Chaindesk. 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 Chaindesk 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 Chaindesk MCP in CrewAI

Install the dependencies with `pip install crewai[tools]`. You can pass the Vinkius URL directly into the `mcps` array on your Agent definition for immediate access.

Yes. Import `MCPServerHTTP` from `crewai.mcp` and use `tool_filter`. This prevents your researcher agent from accidentally calling `delete_agent`.

Your crew can easily string tasks together. Agent A might run `create_agent` first, and only when that succeeds does Agent B execute `upsert_datasource`.

The framework handles stdio, SSE, and Streamable HTTP natively. Vinkius provides the HTTP endpoint, and your Python environment connects without extra configuration.

Customer FAQ queries and private system prompts never leak across sessions. The MCP Server architecture enforces ephemeral, zero-trust execution that wipes all memory the second your crew finishes its task.

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