Plugwise MCP Server

# Scan Network Tool Removal ## Summary The `scan_network` tool has been completely removed from the Plugwise MCP server codebase. This tool previously scanned the local network for Plugwise hubs using passwords from environment variables. ## Changes Made ### Source Code - ✅ Removed `/src/mcp/tools/scan-network.tool.ts` - ✅ Removed import from `/src/mcp/tools/index.ts` - ✅ Removed registration call from `registerAllTools()` - ✅ Removed tool definition from `/src/mcp/server.ts` - ✅ Removed `handleScanNetwork()` method from server - ✅ Removed case handler from `handleToolCall()` switch statement - ✅ Updated connection tool error message in `/src/mcp/tools/connection.tool.ts` ### Documentation - ✅ Updated `/README.md` - removed scan_network examples and workflows - ✅ Updated `/docs/add-hub-guide.md` - removed scan_network from related commands - ✅ Updated `/docs/list-hubs-guide.md` - removed scan_network reference - ✅ Updated `/docs/hub-listing-implementation-summary.md` - changed to reference add_hub - ✅ Updated `/docs/server-description-hub-listing.md` - updated examples and guidance - ✅ Updated `/docs/test-scripts.md` - removed scan_network from feature list - ✅ Updated `/docs/mcp-tools-reference.md` - removed scan_network tool documentation - ✅ Updated `/CHANGELOG.md` - removed scan_network from features list ### Test Scripts - ✅ Updated `/scripts/test-utils.ts` - renamed `discoverHubs()` to `listHubs()` - ✅ Updated `/scripts/test-features.ts` - changed to test list_hubs instead - ✅ Updated `/scripts/test-read-only.ts` - changed to use list_hubs - ✅ Updated `/scripts/test-all.ts` - renamed test function to `testListHubs()` - ✅ Updated `/scripts/workflow-demo.js` - changed to use list_hubs - ✅ Updated `/scripts/test-server-description.ts` - changed to check for add_hub - ✅ Updated `/scripts/verify-hub-description.ts` - updated console message ### Server Description Updates - ✅ Changed hub listing message from "Run the scan_network tool..." to "If you are missing a hub, ask the user for the name of the hub and then use the add_hub tool to add it" - ✅ Updated workflow examples in tool descriptions - ✅ Removed scan_network references from connect tool documentation - ✅ Updated list_hubs tool workflow examples ### Build Verification - ✅ TypeScript compilation successful with no errors - ✅ No scan_network references in compiled dist folder - ✅ All test script files have no TypeScript errors ## Alternative Approach Users should now use the `add_hub` tool to add hubs by their name/ID. The workflow is: 1. Get the hub name/ID from the physical device (8-character alphanumeric) 2. Use `add_hub` tool with the hub name 3. The tool will scan the network to find and add the hub 4. Use `list_hubs` to see all registered hubs 5. Use `connect` to connect to a specific hub ## Impact - The `scan_network` tool is no longer available - Users must manually provide hub names to the `add_hub` tool - No breaking changes to other tools (list_hubs, add_hub, connect remain functional) - All documentation and examples updated to reflect the new workflow