MCP Ticketing
Unizo's Ticketing MCP Server provides a unified, extensible platform for integrating ticketing capabilities directly into AI agents and LLM clients through the Model Context Protocol (MCP). Designed for developers, this guide covers how to install, configure, and interact with the Unizo Ticketing MCP server, with a focus on available tools and required environment setup.
Overview
The Unizo MCP Server enables seamless integration of ticketing systems with AI agents through a standardized interface that abstracts the complexity of different ticketing platforms.
Key Benefits
- Unified Ticketing Interface: Interact with multiple ticketing tools like Jira, GitHub, ServiceNow, and Trello through a normalized set of MCP tools
- AI Agent Compatibility: Fully compatible with Claude, GPT, and any other LLMs supporting the MCP protocol
- Rich Toolset: Full CRUD support, with intelligent connector detection and organization metadata resolution
Available Tools
Tool Reference
Tool Name | Description | Parameters |
---|---|---|
list_services | Lists all available ticketing services | Returns: Service names and metadata |
list_integrations | Lists all active integrations for a specific service | Required: service name Supported: Jira, GitHub, GitLab, Bitbucket, ServiceNow, Trello |
list_organizations | Fetches organizations for a connected integration | Required: integration id/name Returns: Organization metadata and settings |
list_collections | Retrieves collections/projects within an organization | Required: integration id/name, organization id/name Returns: Collection names and identifiers |
confirm_ticket_creation | Validates and extracts ticket details from user request | Required: user_request Returns: Parsed ticket information |
create_ticket | Creates a new support ticket in the connector | Required: integration id/name, organization id/name, collection id/name, ticket name Optional: ticket description, ticket priority (default: High), ticket status (default: OPEN), ticket type (default: Task) |
list_tickets | Retrieves all tickets from integrated ticketing connectors | Required: integration id/name Optional: organization id/name, collection id/name, filters, pagination |
Installation & Setup
Prerequisites
- Node.js or Python runtime (depending on chosen client SDK)
- MCP-capable agent (e.g., Claude, GPT)
- Unizo API credentials (see environment setup below)
Example MCP Server Setup (JSON)
{
"mcpServers": {
"unizo": {
"command": "mcp-proxy",
"args": ["http://172.184.130.51:8999/mcp"],
"env": {
"API_ACCESS_TOKEN": "your_account_token"
}
}
}
}
MCP Server provides a robust foundation for building enterprise-grade AI automation solutions with built-in security, compliance, and scalability features.
Environment Variables
Variable | Description |
---|---|
API_ACCESS_TOKEN | Your Unizo API key for authenticating API requests |
Client Integration Flow
-
Initialize the MCP Server
- Use your preferred orchestrator (Claude Desktop, GPT MCP Plugin, etc.)
- Load the MCP JSON config with the Unizo ticketing setup
-
Query Available Tools - Seamless integration across security and DevOps tool stacks
- Upon server initialization, the tools listed above will be available to the agent
-
Call create_ticket or list_tickets - Designed to handle enterprise-scale AI automation workloads
- Provide required parameters as per tool schema
- Server will route and abstract the integration specifics (e.g., GitHub vs Jira)
Observability & Logging
Unizo MCP server logs every tool invocation with correlation IDs and agent attribution.
Early Access Program
The Unizo Source Code MCP Server is currently available through our Early Access Program. All customers can gain priority access to these powerful identity management tools and receive dedicated implementation support.
Reach out to our team to schedule a personalized demo and discuss integration options for your organization. Connect With Us