Industry solutionsPublic source

Ticketing MCP Server

A service-desk / case-ticketing platform for ADK-Rust Enterprise support, legal, and operations agents. 19 MCP tools covering queues with SLA policies, tickets with priority and auto-computed SLA due dates + breach…

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Queues & SLA policy — each queue defines per-priority response and resolution targets (hours).

Tickets — intake with requester, priority, and tags; SLA deadlines auto-computed from the queue policy × priority. Status workflow: new → open → pending → resolved → closed (closed is…

Triage & assignment — assign to agents (auto-opens new tickets), set priority (recomputes SLA), tag, and escalate (raises priority a notch, bumps escalation level, re-baselines SLA).

Comments — internal notes (staff-only) and public replies (visible to the requester; the first public reply sets the SLA first-response time).

SLA & analytics — sla_status (per-ticket breach flags + minutes remaining), sla_report (open / response-breached / resolution-breached / at-risk-next-2h across a queue), and workload (open…

Architecture

How Ticketing MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Ticketing MCP Server

Validates the request and owns 19 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

Ticketing MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Ticketing MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

19 named tools

create_queue

Create a queue with an SLA policy

internal write

get_queue

Get a queue and its SLA policy

read only

list_queues

List queues

read only

create_ticket

Intake a ticket (auto-computes SLA deadlines)

internal write

get_ticket

Get a ticket by id

read only

list_tickets

List tickets by queue/status/assignee

read only

assign_ticket

Assign a ticket to an agent

internal write

set_priority

Set ticket priority (recomputes SLA)

internal write

set_status

Transition ticket status

internal write

close_ticket

Close a ticket (terminal) — gated

internal write

add_tag

Add a tag to a ticket

internal write

escalate_ticket

Escalate a ticket (raise priority, re-baseline SLA)

internal write

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

9 internal write9 read only1 external write

Two writes are gated (requires_approval): send_public_reply (an external-facing message to the requester — classed external_write) and close_ticket (terminal disposition of a case).…
Workflow integrity — a closed ticket can't be reassigned, re-transitioned, or re-closed; everything is on the audit trail (audit_log).
Reads are read_only. Sample data is fictitious.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-ticketing

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-ticketing",
    ["mcp-ticketing"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md CHANGELOG ↗CHANGELOG.md Architecture ↗docs/architecture.svg Issues and support ↗github.com issues

Keep exploring

Ticketing MCP Server

A purpose-built capability behind one MCP connection.

How Ticketing MCP Server fits into an agent system.

ADK-Rust agent

MCP client

Ticketing MCP Server

Domain system

The server’s published architecture

What can an agent ask Ticketing MCP Server to do?

Understand the effect of every tool.

What the current documentation declares.

Follow the project’s documented starting point.

Continue with the project maintainers’ source of truth.

More in industry solutions.