Earlier versions shipped separate object create, read, update and delete tools; those were folded into the natural-language path, which is where this server is now strongest — asking for SLA breaches or a count of PCs by location and getting a formatted breakdown. It reads through a REST account, so what it can see is exactly what that account's rights allow.
A server over the iTop REST API. It leads with one natural-language query tool that works out which iTop class you mean, alongside a listing of the REST operations your instance exposes.
- smart_query_v2 turns a plain-language question into an iTop query, detecting the target class on its own
- Dedicated handling for ticket classes — user requests, incidents, problems and changes — including SLA and deadline questions
- The same for infrastructure and people: servers, PCs, virtual machines, network devices, persons, teams and organizations
- Grouping and statistical breakdowns: counts by status, by organization, by team
- Friendly field names mapped onto the iTop schema, with fuzzy matching on names, so terms like critical or production land on the right fields
- Software-focused answers when the question is about what is installed on a machine
- list_operations reports the iTop REST operations available on your instance
An iTop instance with its REST API enabled, and an account carrying the REST Services User profile. The server is configured with your instance URL and that account's credentials.
One command plus a key — pip install itop-mcp, then supply credentials