How to Use the Deskpro MCP in CrewAI

Q: Can I restrict which CrewAI agents can modify Deskpro tickets?

Yes. You can use MCPServerHTTP with a toolfilter to expose write tools like updateticketproperties only to your moderator agent. Your research agents can be restricted to read-only tools like listkbarticles.

Q: How does this MCP Server protect Deskpro ticket histories and organization details?

All calls to getticketdetails and listuserorganizations are run inside a zero-trust, ephemeral sandbox environment. Vinkius does not log the payloads or store customer data, ensuring your internal ticket communications remain completely private.

Deploy collaborative teams of specialized agents to manage your Deskpro helpdesk queues using CrewAI and this MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Deskpro MCP to CrewAI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Multi-agent support triage

The `list_helpdesk_tickets` tool provides the raw queue data that your CrewAI research agent uses to identify urgent customer issues. Once identified, a separate coordinator agent uses this information to delegate tasks to specialized resolver agents. This division of labor allows one agent to focus entirely on reading ticket history while another drafts responses. Your crew operates autonomously, moving tickets through your pipeline without manual supervision.

Autonomous profile and ticket enrichment

The `get_user_profile` tool fetches detailed customer history so your CrewAI agents can understand who they are helping. A specialized analyzer agent reviews the customer's organization data using `list_user_organizations` to determine their SLA priority. By sharing memory across the crew, all agents immediately know if the customer belongs to a high-value account. This shared context prevents agents from asking repetitive questions and ensures consistent support.

Automatic ticket resolution via CrewAI MCP Server

The `update_ticket_properties` tool allows your CrewAI closing agent to resolve tickets once the research agent confirms the customer's issue is solved. Operating sequentially, the crew passes the ticket status from open to resolved only after verifying the solution against the knowledgebase. This automated handoff ensures that no ticket is closed prematurely. Your agents collaborate in the background, updating Deskpro status fields only when the entire crew agrees the task is complete.

Setup guide

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

crew.py

from crewai import Agent, Task, Crew

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

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

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

You pass the MCP Server URL to the crew's configuration, allowing all agents to share tools like get_ticket_details. The CrewAI framework manages tool access across your research and resolution agents using its shared memory system.

Yes. You can use MCPServerHTTP with a tool_filter to expose write tools like update_ticket_properties only to your moderator agent. Your research agents can be restricted to read-only tools like list_kb_articles.

Pass your Vinkius connection URL directly into the mcps list when initializing your CrewAI agents. The framework automatically handles the transport protocol, giving your agents instant access to create_new_helpdesk_ticket.

Yes, you can set a manager agent to oversee the crew. The manager checks ticket lists using list_helpdesk_tickets and assigns specific customer issues to subordinate agents for deep analysis.

All calls to get_ticket_details and list_user_organizations are run inside a zero-trust, ephemeral sandbox environment. Vinkius does not log the payloads or store customer data, ensuring your internal ticket communications remain completely private.

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