MCP FOR ITSM
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| apiKey | Yes | API key for authenticating with the ITSM Integration Platform |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_ticketB | Create a new support ticket in the appropriate ITSM system |
| get_ticketA | Retrieve full details of an existing ticket by ID |
| update_ticketB | Update the status, priority, or add a comment to an existing ticket |
| list_ticketsA | List tickets with optional filtering by status, assignee, or system |
| assign_ticketA | Assign a ticket to a specific user |
| add_commentA | Add a comment (public or internal) to an existing ticket |
| search_knowledge_baseA | Search the knowledge base for articles related to an issue |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create-incident-ticket | Guided template for creating a high-priority (P1/P2) incident ticket |
| ticket-status-report | Generate a structured summary of the current ticket queue |
| kb-search-assist | Find relevant knowledge base articles before creating a ticket |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| kb-articles | All knowledge base articles |
| open-tickets | All currently open tickets |
TDQS
Scored across 7 tools
Most tools have distinct purposes, but add_comment and update_ticket both allow adding comments, creating ambiguity. The other tools are clearly separated.
All tools follow a consistent verb_noun snake_case pattern (e.g., create_ticket, list_tickets, search_knowledge_base), making it easy to infer functionality.
Seven tools cover the essential ticket lifecycle and knowledge base search without being excessive, fitting well for an ITSM server.
The tool set covers create, read, update, assignment, and knowledge search, but lacks a delete or archive operation, which may be needed in some workflows.