servicedesk-plus
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SDP_API_KEY | Yes | Your technician key/authtoken from ServiceDesk Plus profile page. | |
| SDP_BASE_URL | Yes | The base URL of your ServiceDesk Plus instance (e.g., productsupport.example.com). | |
| SDP_USERNAME | Yes | Your username/email for ServiceDesk Plus. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_ticketsA | Retrieve, search, and filter ServiceDesk Plus tickets. Args: status: Optional status filter (e.g. 'Open', 'In Progress', 'Closed'). requester_email: Optional requester email address filter. search_query: Optional text keyword search for ticket subjects. row_count: Number of tickets to retrieve (default: 20, max: 100). start_index: 1-based start index for paginated results (default: 1). |
| get_ticketA | Retrieve detailed information on a single ticket, including its status, resolution, and description. Args: ticket_id: The unique numeric ID of the ticket to retrieve. |
| create_ticketA | Create a new Help Desk ticket in ServiceDesk Plus. Args: subject: Short summary or subject of the ticket. description: Full plain-text or HTML description detailing the issue. priority: Optional priority name (e.g. 'High', 'Medium', 'Low'). requester_email: Optional email of the requester. If omitted, uses default. |
| update_ticketA | Update fields on an existing ticket in ServiceDesk Plus. Args: ticket_id: The unique numeric ID of the ticket to update. subject: Optional new subject for the ticket. description: Optional new plain-text or HTML description. status: Optional new status name (e.g. 'Open', 'In Progress', 'Closed'). |
| add_ticket_noteA | Append a technical update or administrative note to a ticket. Args: ticket_id: The unique numeric ID of the ticket. note: Text content of the note to append. |
| list_ticket_notesA | List all notes attached to a specific ticket. Args: ticket_id: The unique numeric ID of the ticket. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/kaattaalan/servicedesk-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server