How to Use the Zendesk MCP in AutoGen

Q: What data types can I access with AutoGen and Zendesk?

The agents work primarily with ticket records from getticket, user details via listusers, and organizational structures defined in Zendesk. The MCP Server provides the raw input for debate.

Q: Can AutoGen check available ticket views for Zendesk?

It uses listviews to understand what reporting dashboards are available. This list feeds into agent discussions, allowing them to recommend which view would best help the human user troubleshoot the issue.

Q: How does AutoGen use Zendesk user data?

Agents can retrieve detailed user profiles using getuser. They then debate if that user's role or status changes the required action on a specific ticket. The discussion is based on this rich input.

Q: What specific data types does this MCP Server touch for privacy?

The primary concern is ticket content and associated user identifiers. The server provides access to the raw interaction data and the structural metadata defining who owns that data.

Get consensus decisions with AutoGen, letting your agents debate Zendesk workflows until they find the answer.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Zendesk MCP to AutoGen

Create your Vinkius account to connect Zendesk to AutoGen 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 Zendesk with AutoGen

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Debating ticket escalation paths

A support issue requires deliberation. You can set up multiple agents to argue over the right path by calling `get_ticket` and having them debate its severity. One agent might insist it needs a macro, while another insists it requires manual intervention. This consensus-driven approach uses the MCP Server to feed the ticket details into an argument pool. The final decision isn't just based on one tool call; it emerges from the group discussion.

Validating agent capabilities

Need to know if a task is within scope? Agents can check available macros using `list_macros` and cross-reference that list with all defined groups via `list_groups`. They debate whether the current issue matches an existing protocol. This simulation helps you build complex routing logic. For instance, Agent A checks tickets with `search_tickets`, Agent B checks the macro availability (`list_macros`), and they argue which combination is best.

Assessing account scope

Before taking action, agents must know what's available. They can use `list_organizations` to understand all defined business units in Zendesk. The resulting list informs a discussion about which scope the current ticket belongs to. This is crucial when building multi-tenant systems. The MCP Server provides the data, and AutoGen handles the 'should we proceed' debate.

Setup guide

Set up Zendesk MCP in AutoGen

Prerequisites

Python 3.10+ installed
autogen-ext[mcp] package
Active Vinkius subscription with a valid endpoint token

1

Install AutoGen with MCP
Run pip install "autogen-ext[mcp]" autogen-agentchat. The MCP extension includes mcp_server_tools for stateless tool access.
2

Fetch tools from the MCP
Call mcp_server_tools(SseServerParams(url=...)) with your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Run your agent
Pass the tools to AssistantAgent and call agent.run(). The agent invokes Zendesk tools and returns structured results.

agent.py

from autogen_ext.tools.mcp import SseServerParams, mcp_server_tools
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient

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

tools = await mcp_server_tools(server_params)

agent = AssistantAgent(
    name="Zendesk_assistant",
    model_client=OpenAIChatCompletionClient(model="gpt-4o"),
    tools=tools,
)

result = await agent.run("List recent Zendesk data")
print(result.messages[-1].content)

Get your connection token →

Prerequisites

Python 3.10+ installed
autogen-ext[mcp] + autogen-agentchat
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Same packages as above. McpWorkbench is ideal when your agent needs stateful sessions across multiple tool calls.
2

Use McpWorkbench as context manager
Wrap your agent in async with McpWorkbench(...) to maintain shared state and resources. The workbench manages the full MCP session lifecycle.
3

Run with workbench
Pass workbench=workbench to your agent. State is preserved across multiple tool calls within the same session.

agent.py

from autogen_ext.tools.mcp import McpWorkbench, SseServerParams
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient

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

async with McpWorkbench(server_params) as workbench:
    agent = AssistantAgent(
        name="Zendesk_assistant",
        model_client=OpenAIChatCompletionClient(model="gpt-4o"),
        workbench=workbench,
    )

    result = await agent.run("List recent Zendesk data")
    print(result.messages[-1].content)

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 Zendesk. 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 Zendesk 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 Zendesk MCP in AutoGen

It doesn't just process them; it makes agents deliberate over the best action for a ticket. If there are competing recommendations, they debate until they reach a consensus on next steps. This is great when simple logic won't cut it.

The agents work primarily with `ticket` records from `get_ticket`, user details via `list_users`, and organizational structures defined in Zendesk. The MCP Server provides the raw input for debate.

It uses `list_views` to understand what reporting dashboards are available. This list feeds into agent discussions, allowing them to recommend which view would best help the human user troubleshoot the issue.

Agents can retrieve detailed user profiles using `get_user`. They then debate if that user's role or status changes the required action on a specific ticket. The discussion is based on this rich input.

The primary concern is `ticket` content and associated user identifiers. The server provides access to the raw interaction data and the structural metadata defining who owns that data.

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