NKS osTicket MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NKS_OSTICKET_URL | Yes | URL of the API entry, e.g. https://support.example.com/api/nks-osticket.php | |
| NKS_OSTICKET_API_KEY | Yes | osTicket API key | |
| NKS_OSTICKET_TIMEOUT_MS | No | Request timeout in milliseconds | 30000 |
| NKS_OSTICKET_REJECT_UNAUTHORIZED | No | Set to false to allow self-signed TLS certificates | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| osticket_list_ticketsA | List tickets, newest first. Filter by status (open/closed/resolved/archived or numeric id) and department. Paginated. |
| osticket_search_ticketsA | Full-text search tickets by subject. Optional status filter and pagination. |
| osticket_get_ticketA | Get one ticket with full detail including the message thread. Each thread entry may include an "attachments" array (fileId, name, type, size, inline, cid); pass an attachment's numeric fileId to osticket_download_attachment. Provide number or id. |
| osticket_get_statsA | Aggregate ticket statistics: total, open, closed, overdue. |
| osticket_list_statusesA | List all ticket statuses with their canonical state. |
| osticket_create_ticketC | Create a new ticket. Requires subject and message. |
| osticket_update_ticketB | Update a ticket: change status, set/clear due date, change help topic, and/or add an internal staff note. |
| osticket_reply_ticketA | Post a customer-facing reply to a ticket. This is emailed to the ticket's user. |
| osticket_delete_ticketA | Permanently delete a ticket and its thread. Irreversible. |
| osticket_link_subticketB | Link a child ticket under a parent (parent/child relationship). |
| osticket_unlink_subticketB | Remove a child ticket's parent link. |
| osticket_get_childrenB | List all child tickets of a parent ticket. |
| osticket_get_parentA | Get the parent ticket of a child ticket (null if none). |
| osticket_download_attachmentA | Download a ticket attachment by its numeric file id (from a thread entry's attachments[].fileId in osticket_get_ticket), returned as base64. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Each tool has a clearly distinct resource/action pairing: ticket CRUD, listing/searching, stats, statuses, replies, attachments, and parent/child linking are all separable. The closest overlap is list_tickets vs search_tickets, but their descriptions make the boundary clear.
All tools use a consistent osticket_ prefix followed by a snake_case verb_noun pattern such as get_ticket, create_ticket, reply_ticket, and link_subticket. The naming is predictable throughout.
Fourteen tools is well within the appropriate range for a ticket-management server. Each tool maps to a meaningful ticket operation without excessive surface area.
Core ticket lifecycle coverage is strong: create, read, update, delete, list, search, reply, stats, statuses, attachments, and parent/child linking are all present. Minor gaps include listing departments/help topics/agents, ticket assignment, and priority management, which agents may need for full osTicket workflows.