fetch_tenant_alertsLABSCO SUMMARY
The daily storage health check, without opening the Storage Insights console.
Everything here reads; nothing reconfigures an array. That makes it a diagnosis surface rather than an administration one — you can ask why response time rose on a system, pull the I/O and data rates over the same window, then list the pools and managed disks behind it in the same conversation. The morning_cup_of_coffee prompt is the shape the author intends: three reads chained and filtered down to what is actually in error.
What it is
A read-only client for the IBM Storage Insights External REST APIs. Thirteen tools cover a tenant's alerts and notifications, the systems registered under it, and per-system performance, capacity and component data.
What you get
- Tenant-level alerts and notifications across everything registered, and the same two scoped to one system id (fetch_tenant_alerts, fetch_tenant_notifications, fetch_system_alerts, fetch_system_notifications).
- The inventory: which storage systems the tenant is monitoring, and the full detail record for any one of them (fetch_storage_systems, fetch_system_details).
- Throughput and latency over a window you choose, given as 20m, 1h or 1d — read, write and total I/O rate; read, write and total data rate; read, write and total response time; and transfer size (fetch_system_io_rate, fetch_system_data_rate, fetch_system_response_time, fetch_system_transfer_size).
- CPU utilization for a system over the same kind of window (fetch_system_cpu_utilization).
- Capacity as used_capacity and available_capacity rather than a single number (fetch_system_capacity).
- Component inventory by type — volumes, pools, enclosures, drives, fc-ports, ip-ports, host-connections, io-groups and managed-disks (fetch_system_components).
- A morning_cup_of_coffee prompt that runs the system, alert and notification reads in sequence and filters the result down to systems in error status, critical alerts and notifications.
Requirements
A Storage Insights tenant ID and an External REST API key, generated through user access management, written into the server's .env as DEFAULT_SI_TENANT_ID and DEFAULT_SI_API_KEY. ADDITIONAL_TENANT_API_MAPPING holds further tenant and key pairs if you want one server across several tenants. uv supplies the Python runtime and the server speaks stdio by default; Streamable HTTP is a reconfiguration rather than a flag. Every per-system tool takes a system_id; fetch_storage_systems lists the storage systems on the tenant, which is where you find it.
Setup effort
Build from source — git clone https://github.com/IBM/ibm-storageinsights-mcpserver.git
USE CASES
01
Starting the day knowing what broke overnight
One prompt pulls systems, alerts and notifications and shows only what is in error or critical.
02
Explaining why an application got slower
Read response time alongside I/O rate and data rate over the same window rather than one metric at a time.
03
Checking whether an array is running out of room
Used and available capacity come back separately, so the headroom is explicit.
04
Finding the component behind an alert
Take the alert on a system, then list its pools, drives or fc-ports to see what the alert points at.
05
Watching load on a system through a busy period
Ask for the last 20m, 1h or 1d of CPU utilization and transfer size instead of watching a dashboard.
13 tools
Listed in project docs. Your client may show a different list.
fetch_tenant_notificationsfetch_storage_systemsfetch_system_notificationsfetch_system_detailsfetch_system_io_ratefetch_system_data_ratefetch_system_response_timefetch_system_transfer_sizefetch_system_cpu_utilizationfetch_system_capacityfetch_system_componentsfetch_system_alertsBEFORE YOU INSTALL
What to know first
Tools you get
13 tools named in the project's documentation. Read-only: every tool is fetch_*. morning_cup_of_coffee is a prompt, not a tool.
Requires
- DEFAULT_SI_TENANT_ID in your environment
- DEFAULT_SI_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/IBM/ibm-storageinsights-mcpserver.git
cd ibm-storageinsights-mcpserverAdd below values to src/si_mcp_server_oss/.env file:
TERMINAL
DEFAULT_SI_TENANT_ID = <YOUR_STORAGE_INSIGHTS_TENANT_ID>
DEFAULT_SI_API_KEY = <YOUR_STORAGE_INSIGHTS_EXTERNAL_REST_API>MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"si_mcp_server": {
"command": "uv",
"args": [
"--directory",
"<YOUR_PATH_TO_PARENT_FOLDER_IBM_STORAGEINSIGHTS>",
"run",
"server.py"
]
}
}
}The configuration on this page does not set DEFAULT_SI_TENANT_ID and DEFAULT_SI_API_KEY; the project's instructions put them in a .env file. Check which folder the server reads that file from before you rely on it.
