list_operationsLABSCO SUMMARY
One question tool instead of a wall of CRUD calls.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
One command plus credentials — pip install itop-mcp, then supply credentials
USE CASES
01
Getting the state of the ticket queue without opening iTop
Ask for open user requests or this week's incidents and get them back grouped by status or priority.
02
Answering an SLA question in a meeting
Ask which tickets breached their SLA, or how on-time completion looks by team, and get the breakdown rather than a raw list.
03
Taking stock of the estate
Count PCs by location or list production servers by organization without hand-writing an OQL query.
04
Checking what the instance actually exposes
List the REST operations available on your iTop before assuming a capability is there.
2 tools
Listed in project docs. Your client may show a different list.
smart_query_v2BEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- python on PATH
- ITOP_PASSWORD in your environment
- ITOP_BASE_URL in your environment
- ITOP_USER in your environment
Where it runs
All 3 documented setups run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
pip install itop-mcpMCP Clients
Claude Desktop — package
CLAUDE DESKTOP — PACKAGE · JSON
{
"mcpServers": {
"itop": {
"command": "itop-mcp",
"env": {
"ITOP_BASE_URL": "<YOUR_ITOP_BASE_URL>",
"ITOP_USER": "<YOUR_ITOP_USER>",
"ITOP_PASSWORD": "<YOUR_ITOP_PASSWORD>",
"ITOP_VERSION": "1.4"
}
}
}
}Claude Desktop — Python source
CLAUDE DESKTOP — PYTHON SOURCE · JSON
{
"mcpServers": {
"itop": {
"command": "python",
"args": [
"-m",
"main"
],
"cwd": "<YOUR_PATH_TO_ITOP_MCP>",
"env": {
"ITOP_BASE_URL": "<YOUR_ITOP_BASE_URL>",
"ITOP_USER": "<YOUR_ITOP_USER>",
"ITOP_PASSWORD": "<YOUR_ITOP_PASSWORD>",
"ITOP_VERSION": "1.4"
}
}
}
}Claude Desktop — Node.js
CLAUDE DESKTOP — NODE.JS · JSON
{
"mcpServers": {
"itop": {
"command": "node",
"args": [
"dist/index.js"
],
"cwd": "<YOUR_PATH_TO_ITOP_MCP>/nodejs",
"env": {
"ITOP_BASE_URL": "<YOUR_ITOP_BASE_URL>",
"ITOP_USER": "<YOUR_ITOP_USER>",
"ITOP_PASSWORD": "<YOUR_ITOP_PASSWORD>",
"ITOP_VERSION": "1.4"
}
}
}
}
