feat!: restructure generic

Author: Jordan Munch O'Hare

.claude/CLAUDE.md

@@ -1,4 +1,4 @@
-# MCP SSH Unraid - Project Instructions
+# MCP SSH SRE - Project Instructions
 
 ## User Expectations
 
@@ -58,4 +58,14 @@ When testing the deployed MCP server, use the MCP tools (e.g., `mcp__unraid-ssh_
 
 ## Filter System
 
-All 79 tools support comprehensive output filtering. Filters are defined in `src/filters.ts` and applied via `...outputFiltersSchema.shape` pattern. When adding new tools, always include filter support.
+All 12 tool modules (with 79+ total actions) support comprehensive output filtering. Filters are defined in `src/filters.ts` and applied via `...outputFiltersSchema.shape` pattern. When adding new tools, always include filter support.
+
+## Platform Architecture
+
+The server uses a platform abstraction layer:
+- **Core tools** (`src/tools/core/`): 10 modules, always loaded on any Linux system
+- **Platform-specific tools** (`src/platforms/*/`): Loaded based on auto-detection
+  - Unraid: 2 modules (array-tools, plugin-tools)
+  - Generic Linux: No extra modules (uses core only)
+
+Tool loading is handled by `src/tool-loader.ts` based on the detected platform.

README.md

@@ -1,10 +1,21 @@
-# MCP SSH Unraid
+# MCP SSH SRE
 
-A Model Context Protocol (MCP) server that provides secure, read-only SSH access to Unraid servers for debugging and monitoring through AI assistants like Claude.
+A Model Context Protocol (MCP) server that provides secure, read-only SSH access to Linux servers for debugging and monitoring through AI assistants like Claude. Supports multiple platforms with auto-detection.
+
+## Supported Platforms
+
+| Platform | Status | Tools |
+|----------|--------|-------|
+| **Unraid** | Full support | 12 modules (10 core + 2 Unraid-specific) |
+| **Generic Linux** | Full support | 10 core modules |
+| **TrueNAS** | Planned | - |
+| **Proxmox** | Planned | - |
+
+The server automatically detects your platform at startup and loads the appropriate tools.
 
 ## Why Use This?
 
-Managing an Unraid server often involves SSH-ing in, running multiple commands, correlating logs, and interpreting system metrics. This MCP server enables AI assistants to do that work for you using natural language.
+Managing a Linux server often involves SSH-ing in, running multiple commands, correlating logs, and interpreting system metrics. This MCP server enables AI assistants to do that work for you using natural language.
 
 **Ask questions like:**
 
@@ -15,90 +26,58 @@ Managing an Unraid server often involves SSH-ing in, running multiple commands,
 
 Instead of manually running `docker logs`, `smartctl`, `docker inspect`, parsing outputs, and correlating information across multiple tools, your AI assistant does it all in seconds.
 
-## Why SSH Instead of the Unraid API?
-
-Unraid 7.2+ includes a [GraphQL API](https://docs.unraid.net/API/), so you might wonder why this project uses SSH instead. The short answer: **the API has significant gaps** for the kind of deep monitoring and debugging this project provides.
-
-### What the Unraid API Cannot Do
-
-The Unraid GraphQL API is still evolving and has documented limitations:
-
-| Feature                                      | API | SSH |
-| -------------------------------------------- | --- | --- |
-| Docker container logs                        | ❌  | ✅  |
-| SMART disk health data                       | ❌  | ✅  |
-| Real-time CPU usage/load averages            | ❌  | ✅  |
-| Network bandwidth monitoring                 | ❌  | ✅  |
-| Disk spin status                             | ❌  | ✅  |
-| Process monitoring (ps/top)                  | ❌  | ✅  |
-| Log file analysis                            | ❌  | ✅  |
-| VM management (libvirt/virsh)                | ❌  | ✅  |
-| GPU monitoring                               | ❌  | ✅  |
-| UPS status                                   | ❌  | ✅  |
-| User scripts                                 | ❌  | ✅  |
-| Security auditing (open ports, SSH sessions) | ❌  | ✅  |
-
-Additionally, the API has a [known 32-bit integer overflow](https://github.com/domalab/ha-unraid-connect/issues/8) affecting memory monitoring on systems with >4GB RAM.
-
-### What SSH Enables
-
-With SSH, this project provides **79 specialized tools** that can:
+## Why SSH Instead of Platform APIs?
 
-- **Analyze Docker logs** - Search, filter, and correlate logs across all containers simultaneously
-- **Parse SMART data** - Detailed drive health analysis including temperature trends, error counts, and failure predictions
-- **Monitor everything** - CPU, memory, I/O, network connections, and processes in real-time
-- **Search logs everywhere** - Pattern matching across syslog, Docker logs, and application logs
-- **Debug inter-container networking** - Test connectivity, DNS resolution, and trace routes between containers
-- **Manage VMs** - Full libvirt/virsh access for VM inspection, VNC details, and QEMU logs
-- **Audit security** - Check open ports, failed logins, certificate expiration, and container privileges
+Many platforms have APIs (like Unraid's GraphQL API), but they often have significant gaps for deep monitoring and debugging:
 
-### Compatibility
+| Feature                                      | APIs | SSH |
+| -------------------------------------------- | ---- | --- |
+| Docker container logs                        | ❌   | ✅  |
+| SMART disk health data                       | ❌   | ✅  |
+| Real-time CPU usage/load averages            | ❌   | ✅  |
+| Network bandwidth monitoring                 | ❌   | ✅  |
+| Process monitoring (ps/top)                  | ❌   | ✅  |
+| Log file analysis                            | ❌   | ✅  |
+| VM management (libvirt/virsh)                | ❌   | ✅  |
+| Security auditing (open ports, SSH sessions) | ❌   | ✅  |
 
-| Approach    | Unraid Version                | Rate Limits |
-| ----------- | ----------------------------- | ----------- |
-| GraphQL API | 7.2+ only (or Connect plugin) | Yes         |
-| SSH         | All versions                  | No          |
-
-### The Bottom Line
-
-The Unraid API is great for basic status checks and container start/stop operations. But for the deep debugging, log analysis, and comprehensive monitoring that AI assistants need to actually diagnose problems, SSH provides unrestricted access to all system tools—on any Unraid version, without rate limiting.
+SSH provides unrestricted access to all system tools on any Linux system, without rate limiting.
 
 ## Features
 
-- **79 specialized tools** for comprehensive Unraid server management through natural language
+- **Auto-detection** - Automatically detects your platform (Unraid, generic Linux) and loads appropriate tools
+- **12 tool modules with 79+ actions** for comprehensive server management through natural language
 - **Dual transport modes** - Run via stdio (local) or HTTP/SSE (network-accessible)
 - **Read-only by design** - Zero risk of accidental system modifications
 - **Docker container management** - Inspect, logs, stats, environment variables, port mappings, network topology, and inter-container communication testing
-- **Storage & array management** - Parity checks, SMART data analysis, drive temperatures, array sync status, mover logs, cache usage, and share configuration
-- **Health diagnostics** - Comprehensive monitoring that aggregates array status, temperatures, disk space, container health, and system resources with automatic issue detection
+- **Storage & array management** - Parity checks, SMART data analysis, drive temperatures, array sync status, mover logs, cache usage, and share configuration (Unraid)
+- **Health diagnostics** - Comprehensive monitoring that aggregates system status, temperatures, disk space, container health, and system resources with automatic issue detection
 - **System monitoring** - Process monitoring, resource usage analysis, disk I/O statistics, network connections, and memory pressure detection
 - **Log analysis** - Search and analyze logs across all containers and system logs simultaneously with pattern detection
 - **VM management** - List, inspect, and monitor virtual machines with VNC connection details and libvirt/QEMU logs
 - **Security auditing** - Port scanning, failed login monitoring, permission audits, and vulnerability scanning
 - **Filesystem operations** - Browse files, search patterns, check permissions, and monitor disk usage with read-only safety
-- **AI-powered insights** - Let Claude correlate data across multiple tools and provide actionable recommendations
-- **Faster troubleshooting** - Diagnose complex issues in seconds instead of manually running multiple commands
 
 ## Quick Start
 
 ### Prerequisites
 
 - Node.js 18 or higher
-- Unraid server with SSH access enabled
+- Linux server with SSH access enabled
 - SSH key pair for passwordless authentication
 
 ### Installation
 
 ```bash
-git clone <repository-url>
-cd mcp-ssh-unraid
+git clone https://github.com/ohare93/mcp-ssh-sre.git
+cd mcp-ssh-sre
 npm install
 npm run build
 ```
 
 ### Configuration
 
-Create a `.env` file with your Unraid server details:
+Create a `.env` file with your server details:
 
 ```bash
 cp .env.example .env
@@ -108,7 +87,7 @@ cp .env.example .env
 Required environment variables:
 
 ```bash
-SSH_HOST=unraid.local          # Your Unraid server hostname or IP
+SSH_HOST=server.local           # Your server hostname or IP
 SSH_PORT=22                     # SSH port (default: 22)
 SSH_USERNAME=mcp-readonly       # Username for SSH connection
 SSH_KEY_PATH=~/.ssh/id_rsa_mcp  # Path to SSH private key
@@ -121,9 +100,9 @@ Add to your MCP client configuration (e.g., Claude Desktop):
 ```json
 {
   "mcpServers": {
-    "unraid-ssh": {
+    "ssh-sre": {
       "command": "node",
-      "args": ["/absolute/path/to/mcp-ssh-unraid/dist/index.js"]
+      "args": ["/absolute/path/to/mcp-ssh-sre/dist/index.js"]
     }
   }
 }
@@ -136,19 +115,19 @@ Add to your MCP client configuration (e.g., Claude Desktop):
 
 For HTTP mode configuration, see the [HTTP/SSE Mode](#httpsse-mode-network-accessible) section below.
 
-## 🔒 Securing Your Deployment
+## Securing Your Deployment
 
 ### Authentication (Required by Default)
 
-OAuth authentication is **REQUIRED by default** in v1.1.0+.
+OAuth authentication is **REQUIRED by default** in v2.0.0+.
 
 Configure via `REQUIRE_AUTH` environment variable:
 
 | Value            | Use Case                                   |
 | ---------------- | ------------------------------------------ |
-| `true` (default) | ✅ Production - require OAuth token        |
-| `false`          | ⚠️ Local dev only - allows unauthenticated |
-| `development`    | ⚠️ Local dev - logs warnings               |
+| `true` (default) | Production - require OAuth token           |
+| `false`          | Local dev only - allows unauthenticated    |
+| `development`    | Local dev - logs warnings                  |
 
 **Never set `REQUIRE_AUTH=false` in production!**
 
@@ -188,8 +167,8 @@ Configure via `REQUIRE_AUTH` environment variable:
 
 ### Network Security
 
-🚫 **DON'T:** Expose directly to internet
-✅ **DO:** Use VPN/Tailscale or reverse proxy with TLS
+- **DON'T:** Expose directly to internet
+- **DO:** Use VPN/Tailscale or reverse proxy with TLS
 
 ### Security Checklist
 
@@ -200,36 +179,32 @@ Configure via `REQUIRE_AUTH` environment variable:
 
 ## Security Setup
 
-For secure access, create a dedicated read-only user on your Unraid server:
+For secure access, create a dedicated read-only user on your server:
 
 ```bash
-# On Unraid server as root
+# On server as root
 useradd -m -s /bin/bash mcp-readonly
 passwd mcp-readonly
 usermod -aG docker mcp-readonly
-
-# Make persistent across reboots
-echo "useradd -m -s /bin/bash mcp-readonly 2>/dev/null" >> /boot/config/go
-echo "usermod -aG docker mcp-readonly 2>/dev/null" >> /boot/config/go
 ```
 
 Generate and deploy SSH key:
 
 ```bash
 # On your local machine
-ssh-keygen -t ed25519 -f ~/.ssh/id_ed25519_mcp -C "mcp-ssh-unraid"
-ssh-copy-id -i ~/.ssh/id_ed25519_mcp.pub mcp-readonly@unraid.local
+ssh-keygen -t ed25519 -f ~/.ssh/id_ed25519_mcp -C "mcp-ssh-sre"
+ssh-copy-id -i ~/.ssh/id_ed25519_mcp.pub mcp-readonly@server.local
 ```
 
 ## Example Usage
 
 Once configured, you can use natural language prompts with your MCP client:
 
-- "List all Docker containers on my Unraid server"
+- "List all Docker containers on my server"
 - "Show me the logs for the Plex container"
 - "What's the current system load and memory usage?"
 - "Run a comprehensive health check"
-- "Check the array status and drive temperatures"
+- "Check the array status and drive temperatures" (Unraid)
 - "Which containers are using the most resources?"
 
 ## Development
@@ -250,29 +225,29 @@ npm run build
 **Choose your deployment mode:**
 
 - **Stdio Mode**: Best for local development or when connecting directly from Claude Desktop on the same machine
-- **HTTP Mode**: Ideal for running on your Unraid server itself or when accessing from remote clients
+- **HTTP Mode**: Ideal for running on your server itself or when accessing from remote clients
 
 ### Stdio Mode (Default)
 
 For use with local MCP clients (like Claude Desktop):
 
 ```bash
 # Build and run with Docker
-docker build -t mcp-ssh-unraid .
-docker run -d --env-file .env mcp-ssh-unraid
+docker build -t mcp-ssh-sre .
+docker run -d --env-file .env mcp-ssh-sre
 
 # Or use Docker Compose
 docker-compose up -d
 ```
 
 ### HTTP/SSE Mode (Network-Accessible)
 
-For remote access or running as a service on your Unraid server:
+For remote access or running as a service on your server:
 
 ```bash
 # Build and run with Docker
-docker build -f Dockerfile.http -t mcp-ssh-unraid-http .
-docker run -d -p 3000:3000 --env-file .env mcp-ssh-unraid-http
+docker build -f Dockerfile.http -t mcp-ssh-sre .
+docker run -d -p 3000:3000 --env-file .env mcp-ssh-sre
 
 # Or use Docker Compose (recommended)
 docker-compose -f docker-compose.http.yml up -d
@@ -286,7 +261,6 @@ In addition to the SSH configuration variables, HTTP mode supports:
 HTTP_PORT=3000                            # Port for HTTP server (default: 3000)
 CORS_ORIGIN=*                             # CORS origin (default: *, allows all origins)
 OAUTH_SERVER_URL=https://mcp.example.com  # Public URL for OAuth discovery (REQUIRED for production)
-MOCK_TOKEN=mcp-unraid-access-token        # Mock token for testing (optional)
 ```
 
 > **Important:** When deploying behind a reverse proxy (Traefik, nginx, etc.), you **must** set `OAUTH_SERVER_URL` to your public URL (e.g., `https://mcp.example.com`). This URL is returned in OAuth discovery metadata endpoints. If not set correctly, OAuth clients will fail with a "protected resource does not match" error.
@@ -305,7 +279,7 @@ Add to your MCP client configuration:
 ```json
 {
   "mcpServers": {
-    "unraid-ssh-http": {
+    "ssh-sre": {
       "url": "http://your-server:3000/mcp",
       "transport": "http"
     }
@@ -318,13 +292,38 @@ Or for Claude Desktop with HTTP support:
 ```json
 {
   "mcpServers": {
-    "unraid-ssh-http": {
-      "url": "http://your-unraid-server.local:3000/mcp"
+    "ssh-sre": {
+      "url": "http://your-server.local:3000/mcp"
     }
   }
 }
 ```
 
+## Architecture
+
+The server uses a platform abstraction layer:
+
+```
+src/
+├── platforms/
+│   ├── types.ts          # Platform interfaces
+│   ├── registry.ts       # Platform detection & registration
+│   ├── linux/            # Generic Linux (baseline)
+│   └── unraid/           # Unraid-specific tools
+├── tools/
+│   └── core/             # 10 core tool modules (all platforms)
+├── tool-loader.ts        # Dynamic tool loading
+├── index.ts              # Stdio transport entry
+└── http-server.ts        # HTTP transport entry
+```
+
+### Adding New Platforms
+
+1. Create `src/platforms/<platform>/index.ts` implementing the `Platform` interface
+2. Add detection logic (file checks, command output parsing)
+3. Create platform-specific tool modules
+4. Register in `src/platforms/index.ts`
+
 ## Contributing
 
 Contributions are welcome! Please ensure:
@@ -340,4 +339,4 @@ ISC
 
 ## Support
 
-For issues and questions, please open an issue on the repository.
+For issues and questions, please open an issue on the [GitHub repository](https://github.com/ohare93/mcp-ssh-sre).

package.json

@@ -1,7 +1,7 @@
 {
-  "name": "mcp-ssh-unraid",
-  "version": "1.1.2",
-  "description": "MCP server for SSH access to Unraid",
+  "name": "mcp-ssh-sre",
+  "version": "2.0.0",
+  "description": "MCP server for SRE operations across multiple platforms via SSH",
   "main": "dist/index.js",
   "type": "module",
   "scripts": {
@@ -17,7 +17,12 @@
   "keywords": [
     "mcp",
     "ssh",
-    "unraid"
+    "sre",
+    "devops",
+    "unraid",
+    "linux",
+    "docker",
+    "monitoring"
   ],
   "author": "",
   "license": "ISC",

src/__tests__/container-topology-tools.test.ts

@@ -1,5 +1,5 @@
 import { describe, it, expect, vi, beforeEach } from 'vitest';
-import { registerContainerTopologyTools } from '../container-topology-tools.js';
+import { registerContainerTopologyTools } from '../tools/core/container-topology-tools.js';
 
 describe('Container Topology Tools', () => {
   let mockServer: any;

src/__tests__/docker-tools.test.ts

@@ -1,5 +1,5 @@
 import { describe, it, expect, vi, beforeEach } from 'vitest';
-import { registerDockerTools } from '../docker-tools.js';
+import { registerDockerTools } from '../tools/core/docker-tools.js';
 
 describe('Docker Tools', () => {
   let mockServer: any;