i-net HelpDesk MCP Server
MCP server that puts the i-net HelpDesk ticket web API in reach of any AI agent — search and read tickets, inspect history, create tickets and apply ticket actions, attachments included.
Check the connection —
server_inforeports configuration and verifies the HelpDesk is reachable with the current credentials (first stop on auth/connection errors).Find tickets —
search_ticketswith the HelpDesk phrase syntax (printer,Resource:"First Level Support"), plus paging (limit,start) andlocale.Read a ticket —
get_ticketreturns fields and attributes;fieldsnarrows the response (full records may hold personal data).Follow the history —
list_ticket_steps(optionallysincea timestamp, bundle steps merged) andget_ticket_stepfor a single step including its text and action.See what's allowed —
list_ticket_actionsmaps currently permitted action ids to display names (ids vary per ticket, user and state).Create tickets —
create_ticketwith requesttext, optional owner, HTML flag,ticket_fields,action_argumentsand attachments.Act on tickets —
apply_ticket_actionanswers, closes, escalates, etc., returning the id of the new editing step; calllist_ticket_actionsfirst.Attach files — inline base64 or (stdio only, within a released directory) a local path;
Attachment,EmbeddedImage,Signature,Unknown; 25 MB/file, 20 files, 50 MB per call.Run it your way — stdio for a local agent, or streamable HTTP/SSE for a shared central instance where each client sends its own bearer token (and optionally
X-Inet-Base-Url).Stay safe on writes —
--read-only,--dry-run,--allowed-actions/--denied-actions,--default-automail; answers are normalized (display values, ISO timestamps, HTML→text,raw: trueto opt out).Note: the README also describes further tools (
get_tickets,get_ticket_conversation,download_attachment,find_unauthorized_tickets,ticket_statisticsand one named tool per ticket action) that are not present in this schema.
Provides tools for interacting with the i-net HelpDesk Ticket Web-API, enabling AI agents to search, read, create, and act on tickets (including answering, closing, escalating) with attachment support, based on the authenticated user's permissions.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@i-net HelpDesk MCP Server search for high priority tickets assigned to me"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
i-net HelpDesk MCP Server
An MCP server that provides the Ticket Web API of i-net HelpDesk as tools for any AI agent: search and read tickets, view processing steps, create new tickets, and execute ticket actions (reply, close, escalate ...) — including file attachments.
The server can be operated in two ways:
Mode | Purpose | Authentication |
stdio | local process per agent (Claude Desktop/Code, Cursor, VS Code…) | Token or user/password from environment variables |
HTTP (streamable) | centrally hosted, multiple users share one server process | each client sends its own |
Requirements
Python 3.10 or newer
An i-net HelpDesk with activated Web API
A user with the right "Web API" — without this right, the server responds with HTTP 403. Which tickets are visible and which actions are allowed depends on the roles of this user.
Related MCP server: tickiti-mcp
Installation
# direkt aus dem Repository ausführen (empfohlen für den Einstieg)
uvx --from git+https://github.com/roddyst/i-net_mcp_server inet-helpdesk-mcp --help
# oder klassisch installieren
pip install git+https://github.com/roddyst/i-net_mcp_serverFor development:
git clone https://github.com/roddyst/i-net_mcp_server
cd i-net_mcp_server
python -m venv .venv && . .venv/bin/activate
pip install -e ".[dev]"
pytestQuickstart: stdio (local agent)
export INET_BASE_URL="https://helpdesk.example.com:9000"
export INET_TOKEN="VGhpcyBpcyBqdXN0IGEgZGVtbyBhY2Nlc3MgdG9rZW4u"
inet-helpdesk-mcpConfiguration for Claude Desktop / Claude Code (claude_desktop_config.json or .mcp.json) — more examples are in examples/:
{
"mcpServers": {
"i-net-helpdesk": {
"command": "uvx",
"args": ["--from", "git+https://github.com/roddyst/i-net_mcp_server", "inet-helpdesk-mcp"],
"env": {
"INET_BASE_URL": "https://helpdesk.example.com:9000",
"INET_TOKEN": "dein-access-token"
}
}
}
}Instead of a token, INET_USERNAME and INET_PASSWORD (Basic Auth) also work. The token is sent as Authorization: Bearer <token>, exactly as described in the i-net documentation.
Quickstart: HTTP (centrally hosted)
inet-helpdesk-mcp --transport http --host 0.0.0.0 --port 8000 \
--base-url https://helpdesk.example.com:9000The endpoint is then at http://<host>:8000/mcp. The agent enters this URL and sends its HelpDesk token in the Authorization header — this is exactly the "URL + Bearer Token" process; the server forwards the header to the HelpDesk. Example for an MCP client that supports remote servers:
{
"mcpServers": {
"i-net-helpdesk": {
"type": "http",
"url": "https://mcp.example.com/mcp",
"headers": { "Authorization": "Bearer dein-access-token" }
}
}
}Without --base-url, the client additionally determines the target system via the X-Inet-Base-Url header. This is practical for tenants with multiple HelpDesk instances but opens the server as a proxy for arbitrary addresses — in an open network, it is therefore better to set a fixed --base-url (then the header is disabled, unless it is allowed with --allow-url-header).
Note on operation: The server does not terminate TLS itself and does not authenticate clients independently — login happens at the HelpDesk with the passed-through token. If it is to be accessible beyond the local network, a reverse proxy with HTTPS should be placed in front of it.
Tools
Tool | Web-API | Description |
| – | Shows the configuration and checks connection + credentials. First stop for errors. |
|
| Find tickets via a search phrase ( |
|
| Fields and attributes of a ticket; |
|
| Currently allowed ticket actions as a map "Id → Display name". |
|
| Processing steps of a ticket, optionally from a timestamp |
|
| A processing step including text. |
|
| Create a new ticket, returns the ticket ID. |
|
| Execute a ticket action, returns the ID of the new processing step. |
create_ticket and apply_ticket_action are not registered at all with --read-only — useful if an agent should only be able to read.
Ticket IDs are accepted both as numbers and in the encoded form that appears in the subject lines of HelpDesk emails.
Typical workflow
search_ticketswith a phrase likeDruckerorResource:"First Level Support"get_ticket/list_ticket_steps/get_ticket_stepto readlist_ticket_actionsto determine the validaction_idapply_ticket_actionwith this ID — the IDs differ per ticket, user, and ticket status, so they must not be guessed.
Ticket fields and action arguments
ticket_fields, step_fields, and action_arguments are optional and are normally not needed. If they are, the rules of the Web API apply: keys must correspond to real field keys (or their localized display names), values are strings; JSON values must be encoded as strings. Examples from the i-net documentation:
{
"ticketextension.dispatchNow": "ALWAYS", // Ticket sofort disponieren
"ticketextension.automail": "NO_MAILS_TO_ENDUSER", // keine Auto-Mails an Endanwender
"processingtimeextension.appointment": "1733875200000", // Wiedervorlage/Termin
"ticketactionextension.escalate": "{'targetResID':'<GUID>','changeTicketStatus':true}"
}Unknown ticket fields lead to an error; unknown action arguments are silently discarded by the HelpDesk and only written to the debug log.
Attachments
Attachments are passed as a list, each with content either inline as Base64 or as a path on the server's file system:
{
"text": "Anfrage mit Anhang",
"attachments": [
{ "name": "screenshot.png", "content_base64": "iVBORw0KGgo…" },
{ "path": "/tmp/protokoll.pdf", "attachment_type": "Attachment" }
]
}path only works in stdio mode, where the agent and server share the same machine; in HTTP modes it is automatically disabled (and can also be disabled for stdio with --no-local-files). Allowed values for attachment_type: Attachment, EmbeddedImage, Signature, Unknown. Maximum per file: 25 MB.
Configuration
Every option is available as an environment variable and as a command-line switch; the command line wins.
Environment Variable | Switch | Default | Meaning |
|
| – | Base URL of the HelpDesk, e.g. |
|
| – | Access token for |
|
| – | Basic Auth as an alternative to the token |
|
|
|
|
|
|
| Bind address for HTTP transports |
|
|
| Port for HTTP transports |
|
|
| Path of the streamable HTTP endpoint |
|
|
| HTTP timeout in seconds |
|
|
| Verify HelpDesk TLS certificate |
|
|
| Hide write tools |
|
| only without | Allow |
|
|
| Allow attachments via file path |
|
|
| Default language for search phrase |
Troubleshooting
Call
server_infofirst — it shows the base URL, auth method, and whether a test query against the HelpDesk works.HTTP 401/403: Token expired or the user lacks the "Web API" right.
HTTP 404 for a ticket: Ticket does not exist or is not visible to this user; tickets that are not yet authorized require the dispatcher role.
Connection errors: Check the base URL including the port (the HelpDesk default is
9000). For self-signed test systems,--no-verify-tlshelps.More details are provided by
--log-level DEBUG(logs go to stderr).
Security notes
Credentials are stored in environment variables or in the
Authorizationheader and are never logged.The server does exactly what the logged-in user is allowed to do — the rights check remains with the HelpDesk.
apply_ticket_actionandcreate_ticketmodify data and can, depending on the configuration, trigger emails to end users. For tests, the action argument"ticketextension.automail": "NEVER"or a test system is recommended.get_ticketby default returns all fields of a ticket, including personal data — restrict it deliberately withfields.
English summary
MCP server exposing the i-net HelpDesk Ticket Web-API: search, read, create and act on tickets, with attachment support. Run it over stdio (credentials from INET_BASE_URL + INET_TOKEN) or over streamable HTTP, where each client authenticates by sending its own Authorization: Bearer <token> header — and, when no base URL is configured, selects the HelpDesk instance with an X-Inet-Base-Url header. Tools: server_info, search_tickets, get_ticket, list_ticket_actions, list_ticket_steps, get_ticket_step, create_ticket, apply_ticket_action. Start with --read-only to expose the reading tools only.
License
MIT. Not an official product of i-net software GmbH. Web API documentation: https://docs.inetsoftware.de/helpdesk/help/webapi.ticket/p/ticket-web-api
Available Tools
8 toolsapply_ticket_actionApply 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 list_ticket_actions first: only the ids listed there are valid, and they differ per ticket, user and state. This changes the ticket, so confirm the action with the user when the intent is ambiguous.
Inputs: action_id (required), ticket_id (required), text, attachments, +4 more. Returns: object
create_ticketCreate ticketA
Create a new ticket and return its id. text is the request text of the ticket. ticket_fields and action_arguments are optional and only needed for advanced cases - unknown ticket fields are rejected, unknown action arguments are ignored by the server.
Inputs: text (required), owner_guid, attachments, html_content, +2 more. Returns: object
get_ticketGet ticketA
Read one ticket with its fields and attributes. Pass fields to limit the response to the entries you need - the full record can be large and may contain personal data.
Inputs: ticket_id (required), fields. Returns: object
get_ticket_stepGet ticket stepA
Read one editing step of a ticket, including its text and the applied ticket action. Pass fields to reduce the returned fields and attributes.
Inputs: step_id (required), ticket_id (required), fields. Returns: object
list_ticket_actionsList 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 apply_ticket_action.
Inputs: ticket_id (required). Returns: object
list_ticket_stepsList 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_step for the text of a single step.
Inputs: ticket_id (required), since. Returns: object
search_ticketsSearch ticketsA
Search tickets with the same phrase syntax as the Tickets application, for example printer or Resource:"First Level Support". Returns the matching ticket ids plus suggestions for fields and values that can narrow the query further.
Inputs: query (required), limit, start, locale. Returns: object
server_infoServer 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.
Inputs: no named parameters. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
MCP server exposing the Backtest360 engine API as tools for AI agents.
AI-native helpdesk hosted in Germany: tickets, replies, KPIs and knowledge base over MCP.
Related MCP Servers
AlicenseAqualityDmaintenanceAn MCP server that lets AI assistants search and read support tickets from Jitbit Helpdesk. Works with both SaaS and on-premise installations.360 npm3MIT
tickiti-mcpofficial
AlicenseBqualityBmaintenanceAn MCP server that exposes the Tickiti helpdesk API to AI assistants, enabling ticket management and helpdesk operations via natural language.11MIT- AlicenseAqualityDmaintenanceMCP server for Otobo ITSM enabling AI assistants to search, create, update, and manage tickets via the Generic Interface REST API.1012 npm1MIT
- AlicenseAqualityDmaintenanceMCP server to manage GestSup tickets via an LLM, with tools for creating, reading, commenting, and searching tickets.13MIT