How to Use the Zammad MCP in LlamaIndex

Q: How do I search for tickets using Zammad and LlamaIndex?

You first use searchtickets to find potential matches. Then, you pass the resulting ticket IDs or metadata into your RAG pipeline. This allows LlamaIndex to index the retrieved data, letting you ask highly specific questions about that ticket's content.

Q: Can I manage user details with Zammad and LlamaIndex?

Absolutely. You can pull user records using getuser or listusers. By indexing this data, you create a persistent knowledge source for HR or admin teams, allowing them to query past employee configurations and roles.

Q: If I want to find old ticket articles using Zammad and LlamaIndex?

You run listticketarticles for the relevant ticket. These results, containing the article bodies, are then fed into your index. You can then query them semantically later on, even if the original keywords aren't present.

Q: Does LlamaIndex support filtering resources when accessing Zammad?

Yes. When setting up the client, you can use allowedtools to filter which operations are available in your index build. This limits the scope of data access and makes your knowledge base more focused.

Build RAG knowledge bases with LlamaIndex using Zammad to index ticket data and configurations.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Zammad MCP to LlamaIndex

Create your Vinkius account to connect Zammad to LlamaIndex 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 Zammad with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Indexing Ticket History with LlamaIndex

Don't just read tickets—make them searchable. You can query past session data by running `get_ticket` for specific IDs, and then indexing that output into your vector store. This turns raw API results into grounded knowledge. When a user asks about 'the issue reported last month,' LlamaIndex finds the relevant ticket articles using `list_ticket_articles`, indexes them, and returns an answer backed by actual Zammad data, not just guesswork.

Semantic Search for Users via LlamaIndex

Need to know who handles what? Run `get_user` or `list_users` and index the resulting user details. Now, if a query comes in like 'who is responsible for billing issues,' your RAG application searches the indexed data and grounds the answer in the actual Zammad user records. This mechanism bypasses simple keyword matching. It understands context. You combine live API data with documents to build a unified knowledge base that's much smarter than a standard helpdesk search bar.

Tracking System Changes using LlamaIndex

Keeping track of system configurations is hard, but not with this MCP Server. Indexing the results from `list_checklists` or `list_slas` allows you to build a searchable repository of operational rules. You can ask, 'What was the SLA for critical tickets in Q1?' and get an indexed answer. LlamaIndex ensures that every piece of API data—from ticket statuses (`list_ticket_states`) to organizational details—becomes part of your queryable index.

Setup guide

Set up Zammad MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all Zammad MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to Zammad tools.",
)
response = await agent.run("List recent Zammad data")

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 Zammad. 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 Zammad 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 Zammad MCP in LlamaIndex

You first use `search_tickets` to find potential matches. Then, you pass the resulting ticket IDs or metadata into your RAG pipeline. This allows LlamaIndex to index the retrieved data, letting you ask highly specific questions about that ticket's content.

Absolutely. You can pull user records using `get_user` or `list_users`. By indexing this data, you create a persistent knowledge source for HR or admin teams, allowing them to query past employee configurations and roles.

The server handles User data. When compliance requires it, you use `data_privacy_delete_user`. Indexing this process helps document that sensitive user records are being removed correctly via a structured API call.

You run `list_ticket_articles` for the relevant ticket. These results, containing the article bodies, are then fed into your index. You can then query them semantically later on, even if the original keywords aren't present.

Yes. When setting up the client, you can use `allowed_tools` to filter which operations are available in your index build. This limits the scope of data access and makes your knowledge base more focused.

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