Skip to content

Troubleshooting Guide

This guide helps resolve common issues when installing or using the F5 XC Cloud Status MCP server.

Root Cause: Node.js or npm is not properly installed or not in your PATH.

Terminal window
# Check if Node.js is installed
node --version # Should be v18.0.0 or higher
npm --version
# If not installed, download from https://nodejs.org

Root Cause: Package not found on npm registry or network issue.

Terminal window
# Clear npm cache
npm cache clean --force
# Check npm registry
npm search @robinmordasiewicz/f5xc-cloudstatus-mcp

Root Cause: npm modules directory permissions.

Terminal window
# Fix npm permissions (recommended)
mkdir ~/.npm-global
npm config set prefix '~/.npm-global'
export PATH=~/.npm-global/bin:$PATH
Terminal window
# Validate your config file
python -m json.tool <config-file>
  • Verify .mcp.json exists in project root
  • Check JSON syntax: python -m json.tool .mcp.json
  • Verify package: npx -y @robinmordasiewicz/f5xc-cloudstatus-mcp@latest --version
  • Fully restart Claude Desktop (not just window)
  • Verify config saved: cat ~/Library/Application\ Support/Claude/claude_desktop_config.json | grep f5xc
  • Restore from backup if corrupted
  • Requires version 1.96.0+ (code --version)
  • Reload window: Cmd+Shift+P → “Developer: Reload Window”
  • Try --add-mcp CLI command
  • Verify config location: ls -la ~/.config/opencode/opencode.json
  • Check mcp section structure
  • Restart OpenCode
Terminal window
# Test F5 Cloud API connectivity
curl -I https://www.f5cloudstatus.com/api/v2/overall
# Should return HTTP 200
  1. Check platform-specific guide
  2. Verify prerequisites (Node.js 18+, npm, internet)
  3. Gather diagnostics: node --version && npm --version
  4. Report issues: https://github.com/robinmordasiewicz/f5xc-cloudstatus-mcp/issues