telecom-ops-claude-code-plugins

telecom-ops-claude-code-plugins is a marketplace of plugins designed to streamline telecom cloud automation. It provides a collection of Claude-based code plugins that integrate with telecom tooling and platforms such as O-RAN O2-IMS/DMS, Nephio, and Kubernetes to support Intent→KRM→GitOps workflows with QoS assurance. The server exposes a set of plugins you can install and run via the MCP (Model Context Protocol) interface, enabling automated orchestration and policy-driven telecom operations. Once started, you can browse available plugins, install or enable specific capabilities, and apply them within your cloud-native telecom environment to automate tasks like resource provisioning, service chaining, and QoS guarantees across Kubernetes clusters and Nephio-managed resources. The tools focus on simplifying automation, improving reliability, and providing an integrated interface for telecom workflow automation.

Prerequisites:

• Node.js (LTS) and npm installed on your machine or build host
• Internet access to fetch the MCP plugin package via npx
• Basic familiarity with MCP workflows and plugin usage

Installation steps:

1. Install Node.js and npm if not already installed. You can download from https://nodejs.org/ or use your system package manager.

2. Verify npm and node are accessible:

   • node -v
   • npm -v

3. Run the MCP server package via npx (no persistent global installation required):

npx -y gemgalawala/telecom-ops-claude-code-plugins

4. Follow any on-screen prompts to initialize and start the plugin marketplace within your MCP environment. If needed, set environment variables to configure logging, plugin cache directory, or custom config path:

export MCP_LOG_LEVEL=INFO
export MCP_PLUGIN_DIR=~/.mcp/plugins
export MCP_CONFIG_PATH=./mcp-config.yaml

5. (Optional) If you maintain a dedicated MCP configuration file, place it at the path defined by MCP_CONFIG_PATH and ensure it references the telecom-ops-claude-code-plugins as a server entry in mcp_config.

6. Validate that the MCP server is running by checking logs or accessing the MCP UI/endpoint as per your environment.

Tips and considerations:

• If you encounter network or download issues with npx, ensure your npm registry is reachable and there are no corporate proxies blocking fetches.
• The plugin set may require access to Kubernetes or Nephio contexts; ensure your kubeconfig and Nephio contexts are configured and accessible to the MCP runtime.
• Use the MCP_LOG_LEVEL environment variable to get more verbose logs during troubleshooting.
• If you plan to customize or persist plugins, configure MCP_PLUGIN_DIR to a writable directory and ensure proper permissions.
• This package is delivered as a plugin marketplace; there may not be a single monolithic server binary. The npx approach fetches and runs the plugin set as needed. If you upgrade, re-run the npx command to fetch the latest version.
• Refer to the project’s release ZIPs for additional plugin variants or platform-specific installers.