Itop MCP Server
iTop service management records access through REST/JSON web services.
Data last scanned today · Reviewed today
Overview
This MCP server bridges your AI agent with iTop, an IT service management platform, using standard REST and JSON protocols. It allows agents to interact with your instance data, functioning as a standalone Symfony web application based on the mcp-bundle framework. To operate the server, you must manually copy your iTop instance's production datamodel XML file into the project directory. The system caches both the datamodel and the list of available webservices with a default TTL of one hour, though this can be cleared via the Symfony console.
Our verdict
The Itop MCP Server is currently in a prototype phase and carries a high risk profile with a security score of 35/100. It is community-maintained rather than official, and critical security aspects such as its authentication method and read-only support have not yet been editorially reviewed. Given its current state, it should be limited to testing and development environments.
- Zero direct dependencies reduce supply-chain risk surface
- Active development with recent commits
- Provides documented integration instructions
- Categorized as a prototype with high risk
- Requires manual synchronization of production datamodel XML files
- Authentication and read-only safety remains unreviewed
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What is required to set up the iTop MCP server?
You must copy the datamodel-production.xml file from your iTop instance into the project's data folder. Additionally, your web server must be configured to serve the /public folder and, if using Apache, it must have mod_rewrite enabled.
›How do I configure the server after installation?
After serving the /public folder, you should browse to the URL and follow the provided on-screen instructions to complete the setup.
›How long is the data and webservice cache held?
The server caches the datamodel and the list of available webservices with a time-to-live (TTL) of 3600 seconds.
›How can I clear the cache manually?
You can clear the cache by running the command bin/console cache:pool:clear --all in your CLI.
Badge
Maintain this server? Add the live badge to your README.