i-net HelpDesk MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INET_HOST | No | Bind-Adresse der HTTP-Transporte | 127.0.0.1 |
| INET_PORT | No | Port der HTTP-Transporte | 8000 |
| INET_TOKEN | No | Access-Token für Authorization: Bearer … | |
| INET_LOCALE | No | Standardsprache der Suchphrase | en |
| INET_TIMEOUT | No | HTTP-Timeout in Sekunden | 30 |
| INET_BASE_URL | No | Basis-URL des HelpDesk, z. B. https://helpdesk.example.com:9000 | |
| INET_PASSWORD | No | Passwort für Basic Auth als Alternative zum Token | |
| INET_USERNAME | No | Benutzername für Basic Auth als Alternative zum Token | |
| INET_HTTP_PATH | No | Pfad des Streamable-HTTP-Endpunkts | /mcp |
| INET_READ_ONLY | No | Schreibende Tools ausblenden | false |
| INET_TRANSPORT | No | stdio, http oder sse | stdio |
| INET_VERIFY_TLS | No | TLS-Zertifikat des HelpDesk prüfen | true |
| INET_ALLOW_URL_HEADER | No | X-Inet-Base-Url-Header erlauben | nur ohne INET_BASE_URL |
| INET_ALLOW_LOCAL_FILES | No | Anhänge per Dateipfad erlauben | true bei stdio, sonst false |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_infoA | Report how this MCP server is configured and verify that the i-net HelpDesk can be reached with the current credentials. Use this first when a call fails with an authentication or connection error. |
| search_ticketsA | Search tickets with the same phrase syntax as the Tickets application, for example |
| get_ticketA | Read one ticket with its fields and attributes. Pass |
| list_ticket_actionsA | List the ticket actions the authenticated user may currently apply to a ticket, as a map of action id to display name. The ids are the input for |
| list_ticket_stepsA | List the editing steps (history) of a ticket. For a primary ticket in a bundle the steps of its secondary tickets are merged in. Use |
| get_ticket_stepA | Read one editing step of a ticket, including its text and the applied ticket action. Pass |
| create_ticketA | Create a new ticket and return its id. |
| apply_ticket_actionA | Apply a ticket action to an existing ticket - answering, closing, escalating and so on - and return the id of the new editing step. Call |
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 8 tools
Each tool targets a distinct operation in the ticket lifecycle: creation, retrieval, search, action listing, action application, step listing, and step reading. No two tools have overlapping purposes, making it easy for an agent to select the correct tool.
Six of eight tools follow a clear verb_noun pattern (e.g., create_ticket, search_tickets, get_ticket). However, server_info is a noun_noun format that breaks the pattern, preventing a perfect score.
With 8 tools, the server covers core ticket operations without being bloated. The number is well-scoped for a focused HelpDesk MCP server, fitting the recommended range comfortably.
The server provides create, read, search, and action application, but lacks a general update tool for modifying ticket fields (e.g., priority, assignee). There is also no delete tool. This is a notable gap, though the action application covers workflow state changes.