Cline ALM X++ MCP Server analyze_upgrade_impact
How to: Cline ALM X++ MCP Server analyze_upgrade_impact
Add ALM X++ MCP Server to Cline
-
01
Open ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"alm-xpp-mcp": {
"url": "https://api.almxpp.com/mcp"
}
}
}-
02
Save the file and restart Cline.
-
03
Ask for something analyze_upgrade_impact does. Cline lists the server's tools on connect and calls analyze_upgrade_impact itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that ALM X++ MCP Server's identifier in your config matches the one above exactly.
Cline's MCP Servers pane edits this file for you if you would rather not find it. Cline docs
Set these first
ALM X++ MCP Server will not start until these are set, so analyze_upgrade_impact never becomes available.
-
ALMXPPMCP_API_KEY
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.